Skip to content
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

Fix CSRF #88

Merged
merged 1 commit into from
Oct 18, 2018
Merged

Fix CSRF #88

merged 1 commit into from
Oct 18, 2018

Conversation

notzippy
Copy link
Contributor

The google http server does not fully populate the Request.URL so this check fails.
I added code to populate the Request.URL fully
closes #83

The google http server does not fully populate the Request.URL so this
check fails.
closes revel#83
@ptman
Copy link
Contributor

ptman commented Oct 18, 2018

Thank you for looking into it.

I assume by google http server you mean the go http server module of revel.

Wouldn't it make sense to fix this in the http server module? Otherwise each filter needs to fix this itself? And what about apps that for some reason want the request url?

@notzippy
Copy link
Contributor Author

No I mean the Go http server, it is not a bug in Revel. see
https://stackoverflow.com/questions/40826664/get-scheme-of-the-current-request-url

@notzippy notzippy merged commit c8b7cbd into revel:develop Oct 18, 2018
@ptman
Copy link
Contributor

ptman commented Oct 18, 2018

Ok, but still, wouldn't it make sense to fix this in revel for all modules, instead of separately in each module?

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.

2 participants