Ticket #154 (closed design: fixed)
Content-Location base-setting problems
|Reported by:||firstname.lastname@example.org||Owned by:||email@example.com|
|Component:||p3-payload||Severity:||Active WG Document|
Browser implementers don't generally implement Content-Location's base-setting semantics, because of a number of cited problems;
1) Servers often set the wrong C-L, so that a non-existent location is given, and/or internal implementation details are exposed. E.g., if a gateway rewrites URLs but doesn't rewrite Content-Location.
2) HTTP's advice to set Content-Location when doing server-driven content negotiation results in links that are relative to a negotiated resource, rather than the desired (non-negotiated) URI.
- Status changed from new to closed
- Resolution set to fixed