When using gzip compression, the auth server appends a "Content-Length" header with a value of 20 to the "204 No Content Response."
it causes the shittyauthclient to crash.
test curl command:
curl -X POST -d '{"accessToken":"52345234-b345f-4333-3330-e56fztuihjf","clientToken":"4fghfhsdrf-c9c5-44tr1-brgb-0rg5667dr445dfc"}' 'http://test.test/validate' -v -H "accept-encoding: gzip"
will retrurn a content length of 20
When requests are made through proxies, the traffic can potentially be compressed using standard HTTP compression methods such as gzip or deflate. However, if the server appends a content-length header to a 204 response, it can cause a client crash.
When using gzip compression, the auth server appends a "Content-Length" header with a value of 20 to the "204 No Content Response." it causes the shittyauthclient to crash.
test curl command:
curl -X POST -d '{"accessToken":"52345234-b345f-4333-3330-e56fztuihjf","clientToken":"4fghfhsdrf-c9c5-44tr1-brgb-0rg5667dr445dfc"}' 'http://test.test/validate' -v -H "accept-encoding: gzip"
will retrurn a content length of 20When requests are made through proxies, the traffic can potentially be compressed using standard HTTP compression methods such as gzip or deflate. However, if the server appends a content-length header to a 204 response, it can cause a client crash.