httpbis: Ticket #6: Fragments allowed in Location

Link:  http://trac.tools.ietf.org/wg/httpbis/trac/ticket/6

Origin:  http://lists.w3.org/Archives/Public/ietf-http-wg-old/1999MayAug/0103.html

Component: p2-semantics

In the description of the Location header [section 14.30], the ABNF for the Location header is given as:

    Location       = "Location" ":" absoluteURI

This and the accompanying text are incorrect because the definition of 'absoluteURI', given in RFC 2396 does not include fragment identifiers. The correct syntax for the Location header is:

    Location       = "Location" ":" absoluteURI [ "#" fragment ]
      

There are circumstances in which a fragment identifier in a Location URL would not be appropriate:

• With a 201 Created response, because in this usage the Location header specifies the URL for the entire created resource.
• With a 300 Multiple Choices, since the choice decision is intended to be made on resource characteristics and not fragment characteristics.
• With 305 Use Proxy.

At present, the behavior in the case where there was a fragment with the original URI, e.g.: http://host1.example.com/resource1#fragment1 where /resource1 redirects to http://host2.example.com/resource2#fragment2 is 'fragment1' discarded? Do you find fragment2 and then find fragment1 within it? We don't have fragment combination rules.

Mails

• Re: Fragments in "Location" field Roy T. Fielding (fielding@kiwi.ics.uci.edu) (1999-08-06)
  • RE: Fragments in "Location" field Larry Masinter (masinter@parc.xerox.com) (1999-08-06)
    • RE: Fragments in "Location" field Scott Lawrence (lawrence@agranat.com) (1999-08-09)
      • RE: Fragments in "Location" field Larry Masinter (masinter@parc.xerox.com) (1999-08-09)
        • Re: Fragments in "Location" field John Stracke (francis@ecal.com) (1999-08-09)
  • Re: Fragments in "Location" field Rodent of Unusual Size (Ken.Coar@Golux.Com) (1999-08-12)
    • RE: Fragments in "Location" field Scott Lawrence (lawrence@agranat.com) (1999-08-16)
• RE: Fragments in "Location" field Henrik Frystyk Nielsen (henrikn@microsoft.com) (1999-08-13)
  • Re: Fragments in "Location" field Roy T. Fielding (fielding@kiwi.ics.uci.edu) (1999-08-14)
• RE: Fragments in "Location" field Henrik Frystyk Nielsen (henrikn@microsoft.com) (1999-08-15)
  • Re: Fragments in "Location" field Roy T. Fielding (fielding@kiwi.ics.uci.edu) (1999-08-15)

Associated Checkins

fielding@gbiv.com (Sat, 22 Dec 2007 00:07:28 GMT)

[73]: Resolve #6: Fragments allowed in Location

History

: comment added; version, resolution, milestone set; status changed (Sat, 22 Dec 2007 00:07:28 GMT)

• status changed from new to closed.
• version set to 00
• resolution set to fixed
• milestone set to 01

Fixed in [73]

: comment added; version changed (Sat, 22 Dec 2007 04:11:30 GMT)

• version changed from 00 to d00.

: comment added; component set (Fri, 28 Dec 2007 16:24:37 GMT)

• component set to auth

This fix is not complete, see < http://greenbytes.de/tech/webdav/draft-lafon-rfc2616bis-01.html#rfc.change.location-fragments.2 >.

: comment added; component changed (Fri, 28 Dec 2007 16:25:04 GMT)

• component changed from auth to semantics.

: comment added; origin set (Sat, 09 Aug 2008 18:38:14 GMT)

• origin set to http://lists.w3.org/Archives/Public/ietf-http-wg-old/1999MayAug/0103.html

Related Information

Issues List Index