Closed h0x91b closed 8 years ago
Hi @h0x91b
I checked and since nginx 1.3.3 the Etag is cleared on gzip responses, and recent versions try to prefix the value with a "W/" when it is a string. You can try to work with the etag as a parameter, receiving the value on the message template. Check the curl examples on how not to use headers.
Long-Poll flow does not work correctly if Etag is not exists... Currently I`d find a workaround, just turned off gzip in /sub location, but it is not suitable for our solution.
It works without the Etag but you have to adjust your client and server. Did you take a look on this doc?
Nice :)) thanks for the doc I will use it
@h0x91b this commit 3da6cb0e03cbda6c3b8c850052c13a43754e48c5 allow to use the Etag header with the gzip filter on.
Not compressed request returns ETag as expected
In case the gzip allowed headers without ETag...