You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We were having issues with mod_wsgi hanging periodically (about 1-2 times a day) that required an apache restart or touching wsgi.py. Eventually it was narrowed down to being related to python social auth, particularly when many users log in at once (beginning of a shift).
So I installed a bit of logging middleware seen here in wsgi.py:
Also, you can see we're using the deprecated api. The issue exists with the default scope (non deprecated) as well, but takes longer to crash since only "email" and "profile" are appended to the header.
The text was updated successfully, but these errors were encountered:
I've introduced a fix, didn't merged the PR #378 because that change ignores the scope defined in the settings (if any). The fix also applies to all the backends, not just Google.
We were having issues with mod_wsgi hanging periodically (about 1-2 times a day) that required an apache restart or touching wsgi.py. Eventually it was narrowed down to being related to python social auth, particularly when many users log in at once (beginning of a shift).
So I installed a bit of logging middleware seen here in wsgi.py:
So we sifted through the apache error logs and found something strange about the Location HTTP header:
and it was quickly becoming larger:
until it finally severs the connection between wsgi.py and mod_wsgi:
The result is slightly under Apache2's default size limit on HTTP headers (8KB), and can no longer be appended to.
So to work around this I had to go into the Google Oauth backend and keep the scope from growing.
it used to be:
There is one other way around this, to add some settings in settings.py:
So it skips the problematic code.
So then, even 600 logins deep (with a script that continuously logs me in and out, I get this (no growth to scope):
Also, you can see we're using the deprecated api. The issue exists with the default scope (non deprecated) as well, but takes longer to crash since only "email" and "profile" are appended to the header.
The text was updated successfully, but these errors were encountered: