|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
The monitoring plugin does not do anymore gzip compression of pages, since v1.40 of the plugin [1].
Jenkins does gzip compression itself for some time now.
Transfer-Encoding: chunked does not seem incorrect and does not need chunklen. According to google and [2] for example, most servlet containers, including Tomcat, will use either Content-Length or Transfer-Encoding: chunked, depending on its bufferSize and on the size of the page.
That said, I do not know why you have gibberish, since only Jenkins is supposed to do gzip now.
Perhaps Jenkins sets the Content-Encoding: gzip even when it does not gzip anything.
I suppose that you have tried to call Jenkins directly, without the Apache proxy, to check if that changes something for the browser? And that you have tried other browsers?
[1] https://wiki.jenkins-ci.org/display/JENKINS/Monitoring#Monitoring-Releasenotes
[2] http://serverfault.com/questions/155558/how-can-i-disable-transfer-encoding-chunked-in-apache-with-http-1-1-responses