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

gateway doesn’t load .eth domains from Host: header #6699

Closed
parkan opened this issue Oct 7, 2019 · 0 comments · Fixed by #6700
Closed

gateway doesn’t load .eth domains from Host: header #6699

parkan opened this issue Oct 7, 2019 · 0 comments · Fixed by #6700
Labels
kind/bug A bug in existing code (including security flaws)

Comments

@parkan
Copy link

parkan commented Oct 7, 2019

Version information:

master

Description:

the changes in #6448 should have allowed us to resolve .eth domains even though it’s not a “real” TLD, but this still fails when the name is passed in Host: header

Works

$ curl 35.241.8.114/ipns/almonit.eth/

Does Not Work

$ curl 35.241.8.114 --header “Host:almonit.eth”

as discussed w @Stebalien, would be A+ to fix this before DevCon starts properly

@parkan parkan added the kind/bug A bug in existing code (including security flaws) label Oct 7, 2019
@parkan parkan changed the title gateway doesn gateway doesn’t load .eth domains from Host: header Oct 7, 2019
Stebalien added a commit that referenced this issue Oct 7, 2019
This should have been handled down inside the DNSLink resolver. Otherwise, we'll
break any name happens to end in `.eth`.

also fixes #6699
Stebalien added a commit that referenced this issue Oct 7, 2019
This should have been handled down inside the DNSLink resolver. Otherwise, we'll
break any name happens to end in `.eth`.

also fixes #6699
Stebalien added a commit that referenced this issue Oct 7, 2019
This should have been handled down inside the DNSLink resolver. Otherwise, we'll
break any name happens to end in `.eth`.

also fixes #6699
ralendor pushed a commit to ralendor/go-ipfs that referenced this issue Jun 6, 2020
This should have been handled down inside the DNSLink resolver. Otherwise, we'll
break any name happens to end in `.eth`.

also fixes ipfs#6699
ralendor pushed a commit to ralendor/go-ipfs that referenced this issue Jun 6, 2020
This should have been handled down inside the DNSLink resolver. Otherwise, we'll
break any name happens to end in `.eth`.

also fixes ipfs#6699
ralendor pushed a commit to ralendor/go-ipfs that referenced this issue Jun 8, 2020
This should have been handled down inside the DNSLink resolver. Otherwise, we'll
break any name happens to end in `.eth`.

also fixes ipfs#6699
ralendor pushed a commit to ralendor/go-ipfs that referenced this issue Jun 8, 2020
This should have been handled down inside the DNSLink resolver. Otherwise, we'll
break any name happens to end in `.eth`.

also fixes ipfs#6699
ralendor pushed a commit to ralendor/go-ipfs that referenced this issue Jun 8, 2020
This should have been handled down inside the DNSLink resolver. Otherwise, we'll
break any name happens to end in `.eth`.

also fixes ipfs#6699
ralendor pushed a commit to ralendor/go-ipfs that referenced this issue Jun 8, 2020
This should have been handled down inside the DNSLink resolver. Otherwise, we'll
break any name happens to end in `.eth`.

also fixes ipfs#6699
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug in existing code (including security flaws)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant