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
{{ message }}
This repository has been archived by the owner on May 30, 2019. It is now read-only.
I just had the issue that a user who previously register on the site with http://, now came back to the site and login was no longer possible, since he now gets https://.
The question is: Shall I do two queries for these cases? Shall I do this on my side, or wouldn't it be better if the django-openid-auth lib would ignore differences of http vs. https?
Please let me know. I can also dig in the code and see if I can find the right points and adjust the code accordingly, but I'd first love to know if this is something you want to have implemented on your side or not.
Oliver
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi!
I just had the issue that a user who previously register on the site with http://, now came back to the site and login was no longer possible, since he now gets https://.
The question is: Shall I do two queries for these cases? Shall I do this on my side, or wouldn't it be better if the django-openid-auth lib would ignore differences of http vs. https?
Please let me know. I can also dig in the code and see if I can find the right points and adjust the code accordingly, but I'd first love to know if this is something you want to have implemented on your side or not.
Oliver
The text was updated successfully, but these errors were encountered: