Re: [w3ctag/spec-reviews] Review origin policy. (#127)

I'm confused at the first bullet above -- `.well-known` has been through the standards process, and the TAG didn't object to it at the time. W3C has used "hard coded paths" in the past (e.g., `P3P.xml`). Sometimes it's necessary to have origin-specific data in a priviledged place; that's what wellknown is for.

Manifests are a **very** different thing and the use cases shouldn't be combined just because they look like each other.

The `Vary` header is necessary because of intermediary caches, and because that's how HTTP works.

HTTP/2 is **not** a license to have verbose headers; they compression context is limited in size, and can't expand infinitely (as this becomes a server resource issue). As I explained in my draft, H2 header compression is oriented to the connection -- meaning a server has to keep a compression context per connection -- whereas origin policy is oriented to the origin, so only one per origin has to be kept server side.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/spec-reviews/issues/127#issuecomment-279285148