-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Change DNSLink url resolution to <gateway>/ipns/<dnslink-domain> #20567
Comments
That looks weird to me. I do agree that it should not redirect to But imho the query parameters should always be preserved. Anyhow, we have some assumptions here so if you could provide some clarity on your case? |
@markg85 the bug discussed here was detected in the version of Brave before fix from brave/brave-core#10694, which is why the bug report uses URL without params. You are correct, query parameters should always be preserved. Could be related to #20320 |
as discussed in slack with @lidel:
|
Verified
Steps:
Confirmed I was redirected to
Verified
Steps:
Confirmed I was redirected to
Verification passed on
Steps:
Confirmed I was redirected to |
Check when both redirect options are enabled in Brave – https://docs.ipfs.io/?foo=bar redirects to https://bafybeifpyppkishqjofl6ahn6ky7udxuo5gn7s7fuzegrncfkm2ltevac4.ipfs.dweb.link/ instead of https://docs-ipfs-io.ipns.dweb.link/?foo=bar – Automatically redirect to IPFS pages via DNSLink when possible" should have precedence over "Redirect IPFS resources to the configured IPFS gateway", but it looks like it is the other way
Update: Currently we take value from DNSLink header and resolve it to urls like
/ipfs/{cid}/path → ipfs://{cid}/path
. Brave should not resolve DNSlink in address bar – it is losing human-readable name and it is replacing permanent address with CID of a snapshot in time – not what users want.Brave should only check if a valid DNSLink is present, and redirect to /ipns/
The text was updated successfully, but these errors were encountered: