-
Notifications
You must be signed in to change notification settings - Fork 696
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--http-websockets
incompatible with --http-auto-gzip
?
#190
Comments
add-header force the addition of the specified header to every request. You are basically forcing auto-gzip to every url. Auto-gzip remove the content-encoding header to avoid decoding error in the browser. You may want to enable auto-gzip only to specific url, using internal routing. An example, enabling auto-gzip for all of the url not starting with /xhr route-if-not = startswith:${PATH_INFO};/xhr addheader:uWSGI-Encoding: gzip |
im not very familiar with websockets, but does that have a transfer encoding or sorts as well? or is websocket traffic compressed inherently/normally by default? i'm think i'm missing what you're trying to say. i was thinking |
websocket traffic (once the connection is established) bypass the whole HTTP logic. It is basically another protocol running on the same connection. Regarding auto-gzip, yes, it is an explicit process, the backend inform the http router that the content can be "gzipped" safely |
ok cool cool, thanks for the info. AFAICT though, once |
with the latest code i can confirm both works, can we close this ? |
sure... i don't even recall what i was trying to do exactly, so your confirmation is as good as any. |
...after i enable
--http-websockets
, uWSGI will no longer set/sendContent-Encoding: gzip
on my XHR requests.why must one set
uWSGI-Encoding: gzip
anyway? is there some problem i'm unaware of, or is this just to allow selective gzipping?config:
The text was updated successfully, but these errors were encountered: