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

Ticket #83 (closed design: fixed)

Opened 7 years ago

Last modified 2 years ago

OPTIONS * and proxies

Reported by: mnot@pobox.com Owned by:
Priority: normal Milestone: 10
Component: p1-messaging Severity: Active WG Document
Keywords: Cc:
Origin: http://www.w3.org/mid/47040E65.9070001@gmx.de

Description

The following text was in RFC2068, but dropped from RFC2616;

If a proxy receives a request without any path in the Request-URI and
the method specified is capable of supporting the asterisk form of
request, then the last proxy on the request chain MUST forward the
request with "*" as the final Request-URI. For example, the request

OPTIONS http://www.ics.uci.edu:8001 HTTP/1.1

would be forwarded by the proxy as

OPTIONS * HTTP/1.1
Host: www.ics.uci.edu:8001

after connecting to port 8001 of host "www.ics.uci.edu".

This makes it impossible for a proxy to forward an OPTIONS * request, because "*" is not a valid URI (as opposed to "/*"). One solution would be to reinstate the text, but that would require proxies to understand a method-specific case.

Change History

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

  • Component set to auth
  • Milestone set to unassigned

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

  • Component changed from auth to semantics

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

  • Milestone changed from unassigned to 06

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

  • Component changed from p2-semantics to p1-messaging

This really is in P1.

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

From [403]:

restore RFC 2068 text describing how to proxy OPTIONS * (addresses #83)

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

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

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

  • Priority set to normal
  • Status changed from closed to reopened
  • Resolution fixed deleted
  • Severity set to Candidate WG Document

See http://lists.w3.org/Archives/Public/ietf-http-wg/2010AprJun/0156.html:

Didn't we reinstate the * rule regarding this? Yes we did.

http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p1-messaging- latest.html#rfc.section.4.1.2

and a trivial editorial correction needed there:

old:

except as noted above to replace a null path-absolute with "/".

new:

except as noted above to replace a null path-absolute with "/" or "*"."

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

From [821]:

note that proxies can rewrite empty paths to "*" as well (for OPTIONS *) (related to #83)

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

  • Milestone changed from 06 to 10

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

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

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

  • Status changed from closed to reopened
  • Resolution incorporated deleted

comment:12 Changed 4 years ago by mnot@pobox.com

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

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

  • Severity changed from Candidate WG Document to Active WG Document
Note: See TracTickets for help on using tickets.