Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

security-proxy - bad HTTP response in case of downstream "connection refused" #961

Closed
pmauduit opened this issue Apr 21, 2015 · 1 comment

Comments

@pmauduit
Copy link
Member

The security-proxy currently returns a "200 - OK" status with a blank content in case of unavailable downstream tomcats.

I think a "502 - Bad gateway" or a "503 - Service unavailable" should be more relevant.

Step to "reproduce":

  • Launch the proxycas tomcat
  • shut down the georchestra tomcat
  • attempt to connect onto http[s]://host/mapfishapp/
@pmauduit pmauduit self-assigned this Apr 21, 2015
@pmauduit pmauduit added this to the 15.06 milestone Apr 21, 2015
@fvanderbiest
Copy link
Member

+1, this would maximize the benefit of having the ErrorDocument setup as per https://github.com/georchestra/georchestra/blob/14.12/doc/setup/apache.md#configuration

These error documents are currently shown (only) when the tomcat-proxycas is unavailable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants