On Sat, 10 Nov 2012 16:45:33 +0200, Gnarlodious <[email protected]>
wrote:
I get the same thing happening. My webapp takes a while to initialize,
but
meanwhile all requests get the error. Upon uploading a new version I run
a
curl command to make it start up, which minimizes the chance a user will
get the error. I also notice that browsers are modernizing to be more
standards-compliant, so that cache handling and request timeout can make
a
diagnosis difficult. Using the curl command to request the first page has
the benefit of being more patient than a browser, and no cache means
obsolete pages are not returned.
I can imagine in the future the mod_wsgi module will send a minimal http
header to prevent the browser from showing an error or cached page during
webapp startup.
-- Gnarlie
But if the error is 404, that comes from server side. No client generates
fake 404 error to my knowledge, it is server response to say that the
requested resource was not found. In this light mod_wsgi sending minimal
http header at start won't do anything since the server *is* sending
header and the browser is getting it. Only that the response is not what
you would expect.
Graham (or others knowing the deep insides of mod_wsgi), is there any case
where Apache would be sending 404 if mod_wsgi is stalling, or will it
always wait for the response from WSGI application or timeout with some
other error? I couldn't imagine Apache sending 404 randomly for a resource
handled by specific handler without the handler itself returning 404.
(could it be the webapp itself is sending 404?)
- Joonas
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en.
