docs: circumvent oddities with SSE and compression

[BenJeau]

Motivation

I was working with SSEs for my personal project and wasn't able to figure out why sometimes I received some events, only if the events were big. Thought it was something with Chrome, Firefox, or Postman. Was able to view the full response with curl but not within the rest.

After trying different things, I saw #2034 (reply in thread) and it fixed my issue.

Solution

The solution is to either remove the compression layer itself or to add an exception for SSEs. I've added a note on that in the docs related to SSEs

[davidpdrsn]

It should be pretty straight forward to fix in tower-http. Would you be up for giving it a shot? There is an issue for it tower-rs/tower-http#420. Should be able to update DefaultPredicate to include event streams.

[BenJeau]

That seems reasonable to add it to DefaultPredicate, opened a PR on tower-http's side tower-rs/tower-http#465

[BenJeau]

With the code merged from tower-http's side, I still think there should be a mention about compression in the Axum's SSE docs - maybe not specifically about tower-http - in case someone uses compression but not with the DefaultPredicate.

@davidpdrsn what do you think? If you think otherwise, feel free to close this PR

[stevenengler]

Just wanted to mention that if you still want compression on your SSE streams rather than disabling it altogether, you can write your own futures_util::stream::Stream that wraps the axum::body::BodyDataStream and compresses and flushes SSE stream events. This avoids the buffering issues with tower's compression middleware. I wrote a small example at #2728 in the hope that someone passing through might find it helpful.