Opened 11 years ago
Closed 10 years ago
#14 closed defect (fixed)
Effective Request URI definition issues
| Reported by: | jeff.hodges@… | Owned by: | draft-ietf-websec-strict-transport-sec@… |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | strict-transport-sec | Version: | 2.0 |
| Severity: | - | Keywords: | |
| Cc: |
Description
https://www.ietf.org/mail-archive/web/websec/current/msg00473.html:
On 2011-08-06 01:34, =JeffH wrote:
...
- Removed any and all dependencies on [I-D.draft-ietf-httpbis-p1-messaging-15], instead depending on [RFC2616] only. Fixes issue ticket #12 <http://trac.tools.ietf.org/wg/websec/trac/ticket/12>. ...
Not sure this is a good idea.
The current text copies a known bug from draft-ietf-httpbis-p1-messaging-15 (see <http://trac.tools.ietf.org/wg/httpbis/trac/changeset/1340>). [ the HTTP method in the example should
OPTIONS rather than GET ]
Also, the ABNF claims it's based on RFC 2616's definitions, but mentions RFC 3986 in ABNF comments. This needs to be checked.
Change History (1)
comment:1 Changed 10 years ago by jeff.hodges@…
- Resolution set to fixed
- Status changed from new 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)