Opened 9 years ago

Closed 7 years ago

Last modified 6 years ago

#185 closed design (fixed)

Location header field payload handling

Reported by: mnot@… Owned by: mnot@…
Priority: normal Milestone: 18
Component: p2-semantics Severity: Active WG Document
Keywords: Cc:

Description

The definition of the Location header differs in various ways of how at least Web browsers need to deal with them to interoperate with content on the Web:

  1. Need to handle relative URIs.
  2. Need to handle with spaces and other invalid URI characters in the same way as done by e.g. HTML and CSS. (Percent-encode them rather than treat it as error.)

I suspect that any other tool that wants to deal with content on the Web would have similar issues. There's some discussion here including two sites this effects:

http://krijnhoetmer.nl/irc-logs/whatwg/20090323#l-152

Attachments (1)

185.diff (1.2 KB) - added by julian.reschke@… 7 years ago.

Download all attachments as: .zip

Change History (13)

comment:1 Changed 9 years ago by mnot@…

  • Owner set to mnot@…

Proposal:

1) allow relative URIs, base is request-URI only 2) syntax is URI, error handling is application-specific

comment:2 Changed 9 years ago by julian.reschke@…

comment:3 Changed 9 years ago by julian.reschke@…

From [785]:

Allow URI-reference instead of URI in Location; state that there are currently no defined precedence rules for fragment identifiers (relates to #43 and #185)

comment:4 Changed 8 years ago by mnot@…

  • Priority changed from normal to blocked

Blocked pending some level of liaison with IRIbis.

comment:5 Changed 8 years ago by mnot@…

#186 (error handling) may have impact.

comment:6 Changed 7 years ago by mnot@…

  • Priority changed from blocked to normal

Changed 7 years ago by julian.reschke@…

comment:7 Changed 7 years ago by julian.reschke@…

From [1496]:

Note that some recipients are lax in processing the Location header field (see #185)

comment:8 Changed 7 years ago by julian.reschke@…

  • Resolution set to incorporated
  • Status changed from new to closed

comment:9 Changed 7 years ago by mnot@…

  • Milestone changed from unassigned to 18

comment:10 Changed 7 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:11 Changed 7 years ago by mnot@…

  • Resolution set to fixed
  • Status changed from reopened to closed

comment:12 Changed 6 years ago by julian.reschke@…

  • Summary changed from Location header payload handling to Location header field payload handling
Note: See TracTickets for help on using tickets.