4 ms·

There is a draft IETF standard to handle this! It uses a new "alt-svc" header that lets you specify alternative URLS to access a domain. Cloudflare is using i

There is a draft IETF standard to handle this! It uses a new "alt-svc" header that lets you specify alternative URLS to access a domain. Cloudflare is using it for their 1.1.1.1 service. If you look at the headers at https://tor.cloudflare-dns.com/ https://tor.cloudflare-dns.com/, you get alt-svc: h2="dns4torpnlfs2ifuz2s2yf3fc7rdmsbhm6rw75euj35pac6ap25zgqad.onion:443"; ma=315360000; persist=1 I don't know if the Tor Browser Bundle handles this yet but its a great idea! https://developers.cloudflare.com/1.1.1.1/fun-stuff/dns-over-tor/ https://developers.cloudflare.com/1.1.1.1/fun-stuff/dns-over... https://tools.ietf.org/html/draft-ietf-httpbis-alt-svc-10 https://tools.ietf.org/html/draft-ietf-httpbis-alt-svc-10

mirimir 8y ago
It looks like HTTP/2 (and specifically alt-svc) is explicitly disabled in Tor browser.[0] > Design Goal: SPDY and HTTP/2 connections MUST be isolated to the URL bar domain. Furthermore, all associated means that could be used for cross-domain user tracking (alt-svc headers come to mind) MUST adhere to this design principle as well. > Implementation status: SPDY and HTTP/2 are currently disabled by setting the Firefox preferences network.http.spdy.enabled, network.http.spdy.enabled.v2, network.http.spdy.enabled.v3, network.http.spdy.enabled.v3-1, network.http.spdy.enabled.http2, network.http.spdy.enabled.http2draft, network.http.altsvc.enabled, and network.http.altsvc.oe to false. Rather than redirection, I was thinking just a fork in rendering, if the user's IP is a Tor exit. 0) https://www.torproject.org/projects/torbrowser/design/ https://www.torproject.org/projects/torbrowser/design/