Add new fix to suggested WSGI config

[Jean85]

This issue emerged in getsentry/sentry-php#857. We found the fix, and this will suggest it.

For reference:

When the enable_compression option was enabled it was affecting only the responses received by the server while first of all the requests should be compressed with GZIP. This PR fixes the problem. Note that if Sentry is running in uWSGI mode and behind a NGINX server as described in the documentation and the client sends a chunked request (as in our case) then a bug in the latter makes the proxied request have both the Transfer-Encoding and Content-Length headers set, which per HTTP/1.1 specs is not valid. For this reason Sentry will be unable to read the request content and will silently discard the event logging an error. The solution is to unset the Transfer-Encoding header in the NGINX config.

[dashed]

Thanks! 👍