https://tools.ietf.org/html/rfc3986#section-3 By placing the scheme within the authority as a tld while using the same authority as the HTTP specification, this probably breaks RFC 3986 and maybe others.
I might be a bit late in saying this.
On Sun, 13 Aug 2017 17:06:20 +0000, Ryan Carboni wrote:
https://tools.ietf.org/html/rfc3986#section-3 By placing the scheme within the authority as a tld while using the same authority as the HTTP specification, this probably breaks RFC 3986 and maybe others.
RFC7686 deals with that.
Andreas
Also: just because it's HTTP/S running over a different network stack, doesn't make it a new scheme.
Just because your dinner arrives on a different plate doesn't mean the recipe has changed. :-)
On 14 Aug 2017 8:53 am, "Andreas Krey" a.krey@gmx.de wrote:
On Sun, 13 Aug 2017 17:06:20 +0000, Ryan Carboni wrote:
https://tools.ietf.org/html/rfc3986#section-3 By placing the scheme within the authority as a tld while using the same authority as the HTTP specification, this probably breaks RFC 3986 and maybe others.
RFC7686 deals with that.
Andreas
-- "Totally trivial. Famous last words." From: Linus Torvalds <torvalds@*.org> Date: Fri, 22 Jan 2010 07:29:21 -0800 _______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
-
Alec Muffett -
Andreas Krey -
Ryan Carboni