* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #185 (closed design: fixed)

Opened 5 years ago

Last modified 2 years ago

Location header field payload handling

Reported by: mnot@pobox.com Owned by: mnot@pobox.com
Priority: normal Milestone: 18
Component: p2-semantics Severity: Active WG Document
Keywords: Cc:
Origin: http://www.w3.org/mid/op.urlt5luv64w2qv@annevk-t60.oslo.opera.com

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

185.diff (1.2 KB) - added by julian.reschke@gmx.de 3 years ago.

Change History

comment:1 Changed 5 years ago by mnot@pobox.com

  • Owner set to mnot@pobox.com

Proposal:

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

comment:2 Changed 5 years ago by julian.reschke@gmx.de

comment:3 Changed 4 years ago by julian.reschke@gmx.de

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 4 years ago by mnot@pobox.com

  • Priority changed from normal to blocked

Blocked pending some level of liaison with IRIbis.

comment:5 Changed 3 years ago by mnot@pobox.com

#186 (error handling) may have impact.

comment:6 Changed 3 years ago by mnot@pobox.com

  • Priority changed from blocked to normal

Changed 3 years ago by julian.reschke@gmx.de

comment:7 Changed 3 years ago by julian.reschke@gmx.de

From [1496]:

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

comment:8 Changed 3 years ago by julian.reschke@gmx.de

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

comment:9 Changed 3 years ago by mnot@pobox.com

  • Milestone changed from unassigned to 18

comment:10 Changed 2 years ago by mnot@pobox.com

  • Status changed from closed to reopened
  • Resolution incorporated deleted

comment:11 Changed 2 years ago by mnot@pobox.com

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

comment:12 Changed 2 years ago by julian.reschke@gmx.de

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