evernat commented on Bug JENKINS-16985

I am of course not an expert at HTTP protocol.
But I know well JENKINS-14050, and the main issue of JENKINS-14050 was not that content was gzipped, but it was that the content was twice gzipped (once by the plugin, and once by Jenkins after some Jenkins version). The Content-Encoding could not be set to gzip+gzip and of course the content could not be understood by the browser.

Anyway, you said "I did upgrade and find that the monitoring plugin did start working properly".
So that's good.

For the deeper issue, I suppose that Jenkins core or Winstone may have an issue with headers.

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.
 
 

Reply via email to