|
||||||||
|
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.
503 Service Unavailable doesn't seem to fit because the server (IIS) is available and handling the request - it is upstream which is broken. Where as 502 Bad Gateway and 504 Gateway Timeout seem like the expected possible responses in this situation, depending on whether the proxy (IIS) could connect to upstream or not.
In any case, it's a trivial fix which doesn't have a downside AFAIK so I just don't understand the point of your comment.