You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The API currently always sends out the stats with HTTP-compression (deflate), regardless of what the client specifies that it can handle. This breaks the HTTP-compression negotiation specified in RFC 2616.
This causes issues for example (in my case) trying to gather statistics from scripts that does not send "Accept-Encoding: deflate" and thus cannot handle the reply without extra decoding.
The text was updated successfully, but these errors were encountered:
The API currently always sends out the stats with HTTP-compression (deflate), regardless of what the client specifies that it can handle. This breaks the HTTP-compression negotiation specified in RFC 2616.
This causes issues for example (in my case) trying to gather statistics from scripts that does not send "Accept-Encoding: deflate" and thus cannot handle the reply without extra decoding.
The text was updated successfully, but these errors were encountered: