Opened 10 years ago
Closed 9 years ago
#397 closed design (fixed)
URI normalization vs empty path
| Reported by: | julian.reschke@… | Owned by: | draft-ietf-httpbis-p1-messaging@… |
|---|---|---|---|
| Priority: | normal | Milestone: | 22 |
| Component: | p1-messaging | Severity: | In WG Last Call |
| Keywords: | Cc: |
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 (6)
comment:1 Changed 10 years ago by fielding@…
comment:2 Changed 10 years ago by mnot@…
In Atlanta;
ACTION: put the exception for OPTIONS request to a proxy and the resulting URI
comment:3 Changed 9 years ago by fielding@…
comment:4 Changed 9 years ago by fielding@…
- Resolution set to incorporated
- Status changed from new to closed
comment:5 Changed 9 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:6 Changed 9 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed
Note: See
TracTickets for help on using
tickets.
![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
yes, needs fixing