Browse Source
Per review feedback: JSON Lines is not only a live event stream like SSE, it's also used for bulk/streamed exports where caching can be legitimate. `Cache-Control: no-cache` forces revalidation and would take away the `max-age` "serve from cache" option from those endpoints, so it shouldn't be imposed by default. Keep only `X-Accel-Buffering: no` (buffering defeats incremental streaming in every case) and leave caching headers to the user. Document the proxy buffering behavior in the JSON Lines tutorial.pull/15813/head
3 changed files with 19 additions and 7 deletions
Loading…
Reference in new issue