Management SSE for apps fails when Accept-Encoding is sent

[gbbirkisson]

You can make the SSE endpoint for apps return a 200 but still fail by adding Accept-Encoding: gzip, deflate to the request headers.

$ curl -v --user 'su:bla' -N \
    -H 'Accept: text/event-stream' \
    -H 'Accept-Encoding: gzip, deflate' \
    http://localhost:4848/app/events

*   Trying 127.0.0.1:4848...
* Connected to localhost (127.0.0.1) port 4848 (#0)
* Server auth using Basic with user 'su'
> GET /app/events HTTP/1.1
> Host: localhost:4848
> Authorization: Basic blabla
> User-Agent: curl/7.73.0
> Accept: text/event-stream
> Accept-Encoding: gzip, deflate
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Date: Mon, 30 Nov 2020 15:30:18 GMT
< Set-Cookie: JSESSIONID=s0rk7cjder9q1ev2utc5xkp5u66; Path=/; HttpOnly
< Expires: Thu, 01 Jan 1970 00:00:00 GMT
< Content-Type: text/event-stream
< Vary: Accept-Encoding
< Content-Encoding: gzip
< Transfer-Encoding: chunked
< 
Warning: Binary output can mess up your terminal. Use "--output -" to tell 
Warning: curl to output it to your terminal anyway, or consider "--output 
Warning: <FILE>" to save to a file.
* Failure writing output to destination
* Failed reading the chunked-encoded stream
* Closing connection 0

Remove the Accept-Encoding header and everything is fine.

[anatol-sialitski]

@gbbirkisson try to use -H 'Content-Type: text/event-stream' -H 'Content-Encoding: gzip, deflate' instead

[rymsha]

@anatol-sialitski
Well, your option will work, but only because it won't have Accept-Encoding header.
Apache Httpclient sends Accept-Encoding, and for (still) unknown reason it is problematic.
I'm on this issue

[rymsha]

Jetty and Resteasy (at least 3.x) SSE implementation don't work well together when client wants gzip (advertises via Accept-Encoding)

Easiest way for now is to disable compression for text/event-stream responses.

[rymsha]

jetty/jetty.project#4317