Working fine on dev box but not functioning on test box with virtual directory about django-maintenance-mode HOT 11 CLOSED

@wjstarrsiii thank you for reporting this. Could you give a look to #74 please? Let me know if it helps...

from django-maintenance-mode.

I put the FORCE_SCRIPT_NAME in place and have all of my application urls, reverse lookups, and functionality working properly with it after some fiddling around. Now /app/maintenance-mode/on/ and /off/ are properly setting the state file, but the resulting redirect takes me to the server root (RHEL apache Test Page). And even if maintenance-mode is on, absolutely nothing is being redirected to the 503 page.

from django-maintenance-mode.

It looks like the PR is trying to resolve the redirect after setting maintenance mode issue, but I don't see anything about the core functionality failing to redirect to 503.

from django-maintenance-mode.

Just to be sure nothing funny was going on with my whitelist pattern matching, I temporarily removed all IGNORE_URLS, it should redirect everything but it still redirects nothing.

from django-maintenance-mode.

@wjstarrsiii could you test if PR #75 solves your problem?

from django-maintenance-mode.

Update... I changed the testing server and moved the application to the root /. WSGIAlias is now /, and FORCE_SCRIPT_NAME is "". there are no whitelisted URL patterns. The application functions fine. the maintenance-mode/ urls still work to set the state but don't redirect properly. Still nothing is redirected to 503 when maintenance mode is set. Might not be related to script_name after all.

from django-maintenance-mode.

It means that this function (called by the middleware) return an unexpected result... if you want to debug the reason you can add some logs before each return statement to identify which one is the cause.

from django-maintenance-mode.

It turns out I am a moron. I put logging all throughout http.py and middleware.py, and nothing was logged. Then I noticed that due to other differences between dev and testing I had restated completely the MIDDLEWARE setting in the testing config. Did I put this middleware in there? Of course not. Now everything is working as expected without a script name in the URL. I suppose I will try to turn that on and off later if I want to / need to put the app back into a virtual directory. Thank you for your help.

from django-maintenance-mode.

@wjstarrsiii don't worry, it happens :)

Since you did some tests with FORCE_SCRIPT_NAME, if you can give some contribute on #74 / #75 it will be appreciated.

from django-maintenance-mode.

I was never able to get anywhere with FORCE_SCRIPT_NAME, some of the internal django redirects were malformed, after research it seems that that is not a straightforward option to use. I may proceed instead using a sub-domain instead of virtual directory so the dynamic portion of urls are not affected.

from django-maintenance-mode.

I never used it, frankly I always use a subdomain in these cases. Thank you for the feedback!

from django-maintenance-mode.