Subject: [websec] #14: Effective Request URI definition issues

From: "websec issue tracker" <[email-masked]>
Date: Wed, 14 Sep 2011 21:44:20 -0000

#14: Effective Request URI definition issues

 https://www.ietf.org/mail-archive/web/websec/current/msg00473.html:

 On 2011-08-06 01:34, =JeffH wrote:

     ...
     12. 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.

-- 
-------------------------------------------+--------------------------------
 Reporter:  jeff.hodges@…                  |       Owner:  draft-ietf-websec-strict-transport-sec@…             
     Type:  defect                         |      Status:  new                                                  
 Priority:  minor                          |   Milestone:                                                       
Component:  strict-transport-sec           |     Version:  2.0                                                  
 Severity:  -                              |    Keywords:                                                       
-------------------------------------------+--------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/websec/trac/ticket/14>
websec <http://tools.ietf.org/websec/>