W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2015

Re: [451] #80: Distinguishing intermediaries from origins

From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Mon, 24 Aug 2015 06:53:34 +0000
To: Mark Nottingham <mnot@mnot.net>
cc: HTTP Working Group <ietf-http-wg@w3.org>, Tim Bray <tbray@textuality.com>
Message-ID: <74369.1440399214@critter.freebsd.dk>
In message <1C63E7B4-B1F6-4F0E-A931-3119959ED7EC@mnot.net>, Mark Nottingham wri

>It's not that hard. if you're the origin server as per HTTP (i.e., your 
>hostname shows up in the URL) - whether it's a CDN or not -
>you're the origin. Otherwise, you're not.

I think the (...) says the exact opposite of what you want:  Most
servers have a single hostname which never appear in URLs, but
serves many URL domains.

But inverting it "(i.e., the domainname in the URL points to your
server)", to match what I think was your intent, isn't much better.

For instance captive gateways where wildcard DNS responses point
everything to a proxy would become 451 rather than 452.

It also leaves the webhosting company to send 451 for AUP reasons,
even though they will disclaim any legal authority over the content
they serve.

As I said:  Nailing gruel to the wall.

>One way to do #3 would be to require / request that the host generating 
>the status code put its name in a header; that would help disambiguate 
>(as long as the origin name was used, and not a deployment name).

I doubt that would happen in reality, there are big incentives to lie.

Leave it at 451 and recommend that the body contains useful details.

Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.
Received on Monday, 24 August 2015 06:53:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:46 UTC