Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] How to turn off Transfer-Encoding: Chunked when sending with jetty client


On Fri, Nov 20, 2015 at 8:22 AM, Tuomas Kiviaho <tuomas.kiviaho@xxxxxx> wrote:
> Greg Wilkins wrote
>> Connection:close cannot be used to delineate the content of a request (as
>> it can be for a response), because some infrastructure does not well
>> support half closed connections - thus the RFC explicitly disallows this.
> Thanks for clearing this one out for me. There it is at at index number 6 on
> RFC 7230
> <>  . I
> guess the comments in the source code were back from the day of RFC 2616.
> HTTP/1.0 suggested earlier doesn't sound appealing, but at least that's
> still a sort of an option. I am sending text/event-stream with the jetty
> client so the chunking sort of caught my eye.
> PS. You asked uses cases couple a months back at
> <>
> and plain old SSE processing could be one. The servlet jetty provides for
> SSE seems a bit outdated now that I saw what you've playing with.

Can you expand on what you mean by "outdated" ?
You mean that you would prefer a ReactiveStreams API for SSE rather
than the API that is provided ?
Are you using

Also you said you are sending text/event-stream from the *client* ?

Simone Bordet
Developer advice, training, services and support
from the Jetty & CometD experts.

Back to the top