Opened 12 years ago
Closed 10 years ago
#222 closed design (fixed)
effective request URI: handling of request-target *
Reported by: | julian.reschke@… | Owned by: | fielding@… |
---|---|---|---|
Priority: | normal | Milestone: | 19 |
Component: | p1-messaging | Severity: | Active WG Document |
Keywords: | Cc: |
Description
The definition of effective request URI currently treats "*" like "/". We need to confirm this is ok.
Change History (9)
comment:1 Changed 12 years ago by fielding@…
comment:2 Changed 11 years ago by mnot@…
- Owner set to fielding@…
comment:3 Changed 11 years ago by julian.reschke@…
we may want to actually define a URI for presenting that request-target, such as
comment:4 Changed 11 years ago by julian.reschke@…
This issue is actually about the abstraction an intermediary uses; they can not assume that the Effective Request URI can be blindly passed from the server to the client.
comment:5 Changed 11 years ago by julian.reschke@…
TODO: check current uses of e-r-u to see whether it needs to allow the OPTIONS-* case.
comment:6 Changed 10 years ago by fielding@…
comment:7 Changed 10 years ago by fielding@…
- Milestone changed from unassigned to 19
- Resolution set to incorporated
- Status changed from new to closed
I have checked all uses and confirm this can be closed.
comment:8 Changed 10 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:9 Changed 10 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed
Note: See
TracTickets for help on using
tickets.
Why doesn't it just say that "*" refers to the server as a whole rather than a specific resource?