-
Notifications
You must be signed in to change notification settings - Fork 31
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
Changes to nginx @maintenance handler #168
base: master
Are you sure you want to change the base?
Conversation
Thanks for opening this @stick. The remaining failing test is the following which makes assumptions about omero-web/test/unit/test_web.py Lines 477 to 507 in 9e0d870
Given the divergence introduced in this PR between these two configuration files, is it worth trying to update the test or should this PR drop it so that we can review it @manics ? |
I'm happy to see us remove |
This pull request has been mentioned on Image.sc Forum. There might be relevant details there: |
Re-opening with #174 in. |
Still failing with:
Perhaps the changes from the uncommented run need adding? |
Conflicting PR. Removed from build OMERO-python-superbuild-push#2. See the console output for more details.
--conflicts |
previous configuration would not display maintenance page if omero.web wasn't running. This was likely due to the request being passed to the @proxy_to_app named location and the configuration not being inherited into that stanza. This commit moves the error_page directive up to the server container where possible or duplicates the directive into the named location directive otherwise. Additionally the return code is set to 502 to avoid situations where returning the maintenance page causes a 200 return code and confusing monitoring systems. (502 is always 502 with the current configuration.
Co-authored-by: Simon Li <[email protected]>
219d9e7
to
06b0073
Compare
previous configuration would not display maintenance page if omero.web
wasn't running. This was likely due to the request being passed to the
@proxy_to_app named location and the configuration not being inherited
into that stanza.
This commit moves the error_page directive up to the server container
where possible or duplicates the directive into the named location
directive otherwise.
Additionally the return code is set to 502 to avoid situations where
returning the maintenance page causes a 200 return code and confusing
monitoring systems. (502 is always 502 with the current configuration.