Skip to content

Added “next” param to form action #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 24, 2019
Merged

Added “next” param to form action #3

merged 1 commit into from
Jun 24, 2019

Conversation

ranbena
Copy link
Contributor

@ranbena ranbena commented Jun 19, 2019

Fixes #2.

Dunno how to test it.
Should work?

@ranbena ranbena requested a review from arikfr June 19, 2019 06:53
@ranbena ranbena self-assigned this Jun 19, 2019
@gabrieldutra
Copy link
Member

Local setup with Redash proxy it seemed to work:

next-login-page

@arikfr arikfr merged commit 1d84ca3 into master Jun 24, 2019
@arikfr
Copy link
Member

arikfr commented Jun 24, 2019

Merged. It will auto deploy soon. If it causes issues just push another change.

@gabrieldutra
Copy link
Member

gabrieldutra commented Jun 24, 2019

Nice to have this working :)

One difference from local and prod for this I just noticed is that locally the url comes Encoded, while in prod it doesn't, this affects multiple Query String parameters on the url (e.g: list pages with search parameters). Still it's better than before.

I actually had in mind to change the host param location to be on the Body and not on the Query (#4 to share the idea in code), I preferred this PR's approach as it seemed safer (only frontend asset changed), but considering the above I opened a new PR with my idea in case it becomes convenient.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Succesful login not redirecting to "/?next"
3 participants