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

Should follow same-origin redirects #25

Open
da2x opened this issue Dec 12, 2019 · 2 comments · May be fixed by #29
Open

Should follow same-origin redirects #25

da2x opened this issue Dec 12, 2019 · 2 comments · May be fixed by #29

Comments

@da2x
Copy link
Contributor

da2x commented Dec 12, 2019

https://staltz.com/.well-known/dat redirects to https://staltz.com/dat which returns a 200 status code and a Dat-DNS file in the expected format. dat-dns treats the redirect as a failure so @staltz’s homepage won’t load in Beaker, however.

dat-dns should follow same-origin (same scheme, domain, and port) redirects. Cross-origin redirects may have security implications. Same-origin redirects should be safe, however.

@staltz
Copy link

staltz commented Dec 13, 2019

So that's why it hasn't worked! Thanks for debugging

@RangerMauve
Copy link
Collaborator

A PR for this would probably be welcome. 😁

da2x added a commit to da2x/dat-dns that referenced this issue Mar 25, 2020
martinheidegger pushed a commit that referenced this issue Mar 26, 2021
martinheidegger pushed a commit that referenced this issue Mar 26, 2021
martinheidegger pushed a commit that referenced this issue Mar 26, 2021
martinheidegger pushed a commit that referenced this issue Mar 26, 2021
@martinheidegger martinheidegger linked a pull request Mar 26, 2021 that will close this issue
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 a pull request may close this issue.

3 participants