|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Interesting attachment.
Here's the problem, it looks like it's not Jenkins who's responding, or it's an irregular response. There's no code path for the console log updates that does not set an X-Something header.
https://github.com/stapler/stapler/blob/master/core/src/main/java/org/kohsuke/stapler/framework/io/LargeText.java#L264
Check your Jenkins log, e.g. on the UI at the /log/all URL. Something may throw an exception to get out of the regular flow. Maybe this is
JENKINS-23971?