|
||||||||
|
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/groups/opt_out.
@hardwickj: very interesting, thanks for noting this. Might help reproduce the stack trace, and is a good tip for people encountering odd errors. (I am wondering whether some incidences of
JENKINS-16474are related.)Bizarre that Apache would produce the totally inappropriate 404 status code for this situation though; I would have expected a 504 here! If you can reproduce that, consider filing a bug for Apache.