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

Ticket #397 (closed design: fixed)

Opened 2 years ago

Last modified 19 months ago

URI normalization vs empty path

Reported by: julian.reschke@gmx.de Owned by: draft-ietf-httpbis-p1-messaging@tools.ietf.org
Priority: normal Milestone: 22
Component: p1-messaging Severity: In WG Last Call
Keywords: Cc:
Origin: http://www.w3.org/mid/508FB6BE.1070401@gmail.com

Description

2.7.3. http and https URI Normalization and Comparison

Likewise, an empty path component is equivalent to an absolute path of "/", so the normal form is to provide a path of "/" instead.

Except that an empty path is not equivalent to a path of "/" in an OPTIONS request sent to a proxy...

Change History

comment:1 Changed 2 years ago by fielding@gbiv.com

yes, needs fixing

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

In Atlanta;

ACTION: put the exception for OPTIONS request to a proxy and the resulting URI

comment:3 Changed 2 years ago by fielding@gbiv.com

From [2038]:

Special case of OPTIONS for normalizing empty path; addresses #397

comment:4 Changed 2 years ago by fielding@gbiv.com

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

comment:5 Changed 19 months ago by mnot@pobox.com

  • Status changed from closed to reopened
  • Resolution incorporated deleted

comment:6 Changed 19 months ago by mnot@pobox.com

  • Status changed from reopened to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.