#154 closed design (fixed)
Content-Location base-setting problems
Reported by: | mnot@… | Owned by: | mnot@… |
---|---|---|---|
Priority: | normal | Milestone: | unassigned |
Component: | p3-payload | Severity: | Active WG Document |
Keywords: | Cc: |
Description
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.
See also:
https://bugzilla.mozilla.org/show_bug.cgi?id=241981 https://bugzilla.mozilla.org/show_bug.cgi?id=238654
Change History (5)
comment:1 Changed 14 years ago by mnot@…
comment:2 Changed 14 years ago by mnot@…
- Owner set to mnot@…
- Priority set to normal
Proposal:
Remove base-setting semantics for HTTP content-location header. Note that this differs from the MIME header of same name.
comment:3 Changed 13 years ago by julian.reschke@…
comment:4 Changed 13 years ago by mnot@…
- Resolution set to fixed
- Status changed from new to closed
Two proposals, both by Roy: