- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Thu, 16 Jul 2015 13:07:17 -0700
- To: Guille -bisho- <bishillo@gmail.com>
- Cc: Ben Maurer <ben.maurer@gmail.com>, Amos Jeffries <squid3@treenet.co.nz>, HTTP Working Group <ietf-http-wg@w3.org>
On 16 July 2015 at 13:03, Guille -bisho- <bishillo@gmail.com> wrote: > No if we don't allow self-reference. www.foo.com can only disable > revalidations on other *different* domains and those are effective for > sub-resources only, no direct page navigations. That's a bizarre limitation. It means that you have to own or use servers (or two names) in order to use the feature. That's a pretty arbitrary limitation. It also doesn't work, because if you do own the two names, you can use one to freeze the other. Like I said, you can implement your proposed solution today, without writing any standards. Sure, only Chrome supports it right now, but that's a whole lot more of the web than none of it.
Received on Thursday, 16 July 2015 20:07:44 UTC