Skip to content
This repository was archived by the owner on Nov 24, 2022. It is now read-only.

Yet another proposed JS reload to the login page#19

Open
DrTrills wants to merge 1 commit into
te-con:masterfrom
DrTrills:patch-2
Open

Yet another proposed JS reload to the login page#19
DrTrills wants to merge 1 commit into
te-con:masterfrom
DrTrills:patch-2

Conversation

@DrTrills

@DrTrills DrTrills commented Jun 5, 2014

Copy link
Copy Markdown
Contributor

Fixed errors on GCE, probably a good idea to add to the entire project as it will work with any system/config. I found adding /login helped the issues with redirecting as it checks if the user is logged in and will re-direct them accordingly. Cuts down on redirects which is not only bad, but can confuse some browsers when switching from http->https

Fixed errors on GCE, probably a good idea to add to the entire project as it will work with any system/config. I found adding /login helped the issues with redirecting as it checks if the user is logged in and will re-direct them accordingly. Cuts down on redirects which is not only bad, but can confuse some browsers when switching from http->https

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why the setTimeout after the window.location.replace? to let Google boot the app?

also why redirecting to eh/login instead of eh/? When someone still has a session he still ends up at the login page or is there something that I'm missing?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants