fix: handle both 503 a 502 http codes the same
Description
fix: handle both 503 a 502 http codes the same
- For new deployments, tomcat doesn't run on localhost, so if it's not running, we get bad gateway instead, so lets treat both codes the same.
How to test
not necessary
Author's checklist
-
I have followed the contribution guidelines -
This MR has been tested or does not change functionality -
I have added relevant merge request dependencies (if this MR has any) -
I have added the correct labels -
I have assigned reviewers (if any are relevant) -
I have edited the documentation (if the changes require it) or I have noted the need for the change if I do not have access to the documentation -
I have marked all introduced BREAKING CHANGES or necessary DEPLOYMENT NOTES in the commit message(s)
Reviewer's checklist
-
This MR has been tested or does not change functionality -
This MR has correct commit message format
Other information
none
Related issues
none