My bad. I should have clarified. Changing process 2 to 1 fixed the specific issue. I no longer get the error after getting authenticated. I am seeing the expected page, now. Thank you!
On Monday, September 10, 2018 at 5:07:48 PM UTC-7, Graham Dumpleton wrote: > > Okay, I assumed when you said 'Authorization' with a capital 'A', that you > were using HTTP Basic Auth, you aren't. > > Instead you are using forms based auth. > > You don't need: > > WSGIPathAuthorization On > > You then need to either use a real database for session storage, or set > the number of process in the daemon process group to 1 instead of 2. > > Right now what is likely happening is that an in memory session store is > being used, which means that when a subsequent request gets handled by the > other daemon process, it doesn't know about you, as you are not in its > separate copy of the session store. > > On 11 Sep 2018, at 5:11 am, userneedshelp <[email protected] > <javascript:>> wrote: > > Graham, I am attaching the debug log here. > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > To post to this group, send email to [email protected] <javascript:> > . > Visit this group at https://groups.google.com/group/modwsgi. > For more options, visit https://groups.google.com/d/optout. > <WSGI_DEBUGGING_SESSIONS.txt> > > > -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
