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.

Sign up for GitHub

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

Jump to bottom

feat(gw): DNSLink names on https:// subdomains #7847

Merged
merged 3 commits into from
Jan 14, 2021
Merged

feat(gw): DNSLink names on https:// subdomains #7847

merged 3 commits into from
Jan 14, 2021

Commits on Jan 1, 2021

  1. feat(gw): support inlined DNSLink names with TLS 

    Problem statement and rationale for doing this can be found under
"Option C" at: ipfs/in-web-browsers#169

TLDR is:

`https://dweb.link/ipns/my.v-long.example.com` can be loaded from a
subdomain gateway with a wildcard TLS cert if represented as a single
DNS label: `https://my-v--long-example-com.ipns.dweb.link`
    @lidel
    lidel committed Jan 1, 2021
    Configuration menu
    Copy the full SHA
    09178aa View commit details
    Browse the repository at this point in the history

Commits on Jan 7, 2021

  1. test: false for isHTTPSRequest 

    As suggested in
#7847 (comment)
    @lidel
    lidel committed Jan 7, 2021
    Configuration menu
    Copy the full SHA
    88dd257 View commit details
    Browse the repository at this point in the history

Commits on Jan 14, 2021

  1. fix: check if rootID has DNSLink before uninlining 

    This kinda enables to run their custom DNS resolver with custom
tlds/names that are independent from the public DNS network.
    @lidel
    lidel committed Jan 14, 2021
    Configuration menu
    Copy the full SHA
    f932510 View commit details
    Browse the repository at this point in the history