$Date: 2007/12/22 23:18:50 $
$Revision: 1.36 $
This is the old issues list pre-WG; please see the new WG issues list.
RFC2616 | total | |
---|---|---|
active | 60 | 60 |
closed | 34 | 34 |
total | 94 | 94 |
id | title | target | type | |
---|---|---|---|---|
i19 | Bodies on GET (and other) requests | RFC2616 | design | |
i20 | Default charsets for text media types | RFC2616 | design | |
i21 | PUT side effects | RFC2616 | design | |
i22 | ETag (and other metadata) in status messages | RFC2616 | design | |
i23 | no-store invalidation | RFC2616 | design | |
i24 | Requiring Allow in 405 responses | RFC2616 | design | |
i27 | PUT idempotency | RFC2616 | design | |
i28 | Connection closing | RFC2616 | design | |
i29 | Age calculation | RFC2616 | design | |
i30 | Header LWS | RFC2616 | design | |
i32 | OPTIONS * | RFC2616 | design | |
i33 | TRACE security considerations | RFC2616 | design | |
i34 | Updated reference for URIs | RFC2616 | design | |
i35 | Split Normative and Informative references | RFC2616 | design | |
i37 | Vary and non-existant headers | RFC2616 | design | |
i38 | Mismatched Vary | RFC2616 | design | |
i39 | ETag uniqueness | RFC2616 | design | |
i41 | Security Considerations | RFC2616 | design | |
i43 | Fragment combination / precedence during redirects | RFC2616 | design | |
i51 | HTTP-date vs. rfc1123-date | RFC2616 | design | |
i54 | Definition of 1xx Warn-Codes | RFC2616 | design | |
i58 | What identifies an HTTP resource | RFC2616 | design | |
i61 | Redirection vs. Location | RFC2616 | design | |
i63 | Header length limit with encoded words | RFC2616 | design | |
i64 | WS in quoted-pair | RFC2616 | design | |
i69 | Clarify "Requested Variant" | RFC2616 | design | |
i70 | Cacheability of 303 response | RFC2616 | design | |
i71 | Examples for ETag matching | RFC2616 | design | |
i73 | Clarification of the term "deflate" | RFC2616 | design | |
i74 | Character encodings for Headers | RFC2616 | design | |
i75 | RFC2145 Normative | RFC2616 | design | |
i76 | Deprecate 305 Use Proxy | RFC2616 | design | |
i77 | Line folding | RFC2616 | design | |
i78 | Relationship between 401, Authorization and WWW-Authenticate | RFC2616 | design | |
i79 | Content-* vs. PUT | RFC2616 | design | |
i80 | Content-Location isn't special | RFC2616 | design | |
i81 | Content Negotiation for media types | RFC2616 | design | |
i83 | OPTIONS * and proxies | RFC2616 | design | |
i85 | Custom Ranges | RFC2616 | design | |
i88 | 205 Bodies | RFC2616 | design | |
i89 | If-* and entities | RFC2616 | design | |
i90 | Delimiting messages with multipart/byteranges | RFC2616 | design | |
i93 | Repeating single-value headers | RFC2616 | design | |
i94 | Reason-Phrase BNF | RFC2616 | design | |
i13 | Updated reference for language tags | RFC2616 | editorial | |
i36 | ABNF | RFC2616 | editorial | |
i40 | Header registration | RFC2616 | editorial | |
i50 | Misc. Typos | RFC2616 | editorial | |
i52 | Sort 1.3 Terminology | RFC2616 | editorial | |
i53 | Allow is not in 13.5.2 | RFC2616 | editorial | |
i55 | Updating to RFC4288 | RFC2616 | editorial | |
i56 | 6.1.1 can be misread as a complete list | RFC2616 | editorial | |
i57 | Status Code and Reason Phrase | RFC2616 | editorial | |
i59 | Status Code Registry | RFC2616 | editorial | |
i60 | 13.5.1 and 13.5.2 | RFC2616 | editorial | |
i67 | Quoting Charsets | RFC2616 | editorial | |
i72 | Request Method Registry | RFC2616 | editorial | |
i82 | rel_path not used | RFC2616 | editorial | |
i91 | Duplicate Host header requirements | RFC2616 | editorial | |
i92 | Empty Host Headers - BNF | RFC2616 | editorial |
id | title | target | type | draft |
---|---|---|---|---|
i1 | HTTP Version should be case sensitive | RFC2616 | design | 01 |
i3 | Chunk Size Definition | RFC2616 | design | 01 |
i5 | Via is a MUST | RFC2616 | design | 01 |
i6 | Fragments allowed in Location | RFC2616 | design | 01 |
i10 | Safe Methods vs Redirection | RFC2616 | design | 01 |
i11 | URI includes query | RFC2616 | design | 01 |
i12 | Invalidation after Update or Delete | RFC2616 | design | 01 |
i14 | Clarification regarding quoting of charset values | RFC2616 | design | 01 |
i15 | No close on 1xx responses | RFC2616 | design | 01 |
i17 | Revise description of the POST method | RFC2616 | design | 01 |
i18 | Cache validators in 206 responses | RFC2616 | design | 01 |
i25 | Accept-Encoding BNF | RFC2616 | design | 04 |
i31 | qdtext BNF | RFC2616 | design | 04 |
i62 | Whitespace in quoted-pair | RFC2616 | design | |
i2 | 'unsafe' characters | RFC2616 | editorial | 01 |
i4 | Message Length | RFC2616 | editorial | 01 |
i7 | Editors Notes | RFC2616 | editorial | 01 |
i8 | Media type registrations | RFC2616 | editorial | 04 |
i9 | Trailer | RFC2616 | editorial | 01 |
i16 | Remove 'identity' token references | RFC2616 | editorial | 01 |
i26 | Import query BNF | RFC2616 | editorial | 04 |
i42 | RFC2606 compliance | RFC2616 | editorial | 02 |
i44 | Unneeded references | RFC2616 | editorial | 04 |
i45 | RFC977 reference | RFC2616 | editorial | 03 |
i46 | references to RFC1700 | RFC2616 | editorial | 03 |
i47 | inconsistency in date format explanation | RFC2616 | editorial | 04 |
i48 | Date reference typo | RFC2616 | editorial | 03 |
i49 | Connection header text | RFC2616 | editorial | 03 |
i65 | Informative references | RFC2616 | editorial | 04 |
i66 | ISO-8859-1 Reference | RFC2616 | editorial | 04 |
i68 | Encoding References Normative | RFC2616 | editorial | 04 |
i84 | Redundant cross-references | RFC2616 | editorial | 04 |
i86 | Normative up-to-date references | RFC2616 | editorial | 04 |
i87 | typo in 13.2.2 | RFC2616 | editorial | 04 |
i1 | HTTP Version should be case sensitive | RFC2616 - design - closed |
|
||
i2 | 'unsafe' characters | RFC2616 - editorial - closed |
|
||
i3 | Chunk Size Definition | RFC2616 - design - closed |
|
||
i4 | Message Length | RFC2616 - editorial - closed |
|
||
i5 | Via is a MUST | RFC2616 - design - closed |
|
||
i6 | Fragments allowed in Location | RFC2616 - design - closed |
|
||
i7 | Editors Notes | RFC2616 - editorial - closed |
|
||
i8 | Media type registrations | RFC2616 - editorial - closed |
|
||
i9 | Trailer | RFC2616 - editorial - closed |
|
||
i10 | Safe Methods vs Redirection | RFC2616 - design - closed |
|
||
i11 | URI includes query | RFC2616 - design - closed |
|
||
i12 | Invalidation after Update or Delete | RFC2616 - design - closed |
|
||
i13 | Updated reference for language tags | RFC2616 - editorial - active |
|
||
i14 | Clarification regarding quoting of charset values | RFC2616 - design - closed |
|
||
i15 | No close on 1xx responses | RFC2616 - design - closed |
|
||
i16 | Remove 'identity' token references | RFC2616 - editorial - closed |
|
||
i17 | Revise description of the POST method | RFC2616 - design - closed |
|
||
i18 | Cache validators in 206 responses | RFC2616 - design - closed |
|
||
i19 | Bodies on GET (and other) requests | RFC2616 - design - active |
|
||
i20 | Default charsets for text media types | RFC2616 - design - active |
|
||
i21 | PUT side effects | RFC2616 - design - active |
|
||
i22 | ETag (and other metadata) in status messages | RFC2616 - design - active |
|
||
i23 | no-store invalidation | RFC2616 - design - active |
|
||
i24 | Requiring Allow in 405 responses | RFC2616 - design - active |
|
||
i25 | Accept-Encoding BNF | RFC2616 - design - closed |
|
||
i26 | Import query BNF | RFC2616 - editorial - closed |
|
||
i27 | PUT idempotency | RFC2616 - design - active |
|
||
i28 | Connection closing | RFC2616 - design - active |
|
||
i29 | Age calculation | RFC2616 - design - active |
|
||
i30 | Header LWS | RFC2616 - design - active |
|
||
i31 | qdtext BNF | RFC2616 - design - closed |
|
||
i32 | OPTIONS * | RFC2616 - design - active |
|
||
i33 | TRACE security considerations | RFC2616 - design - active |
|
||
i34 | Updated reference for URIs | RFC2616 - design - active |
|
||
i35 | Split Normative and Informative references | RFC2616 - design - active |
|
||
i36 | ABNF | RFC2616 - editorial - active |
|
||
i37 | Vary and non-existant headers | RFC2616 - design - active |
|
||
i38 | Mismatched Vary | RFC2616 - design - active |
|
||
i39 | ETag uniqueness | RFC2616 - design - active |
|
||
i40 | Header registration | RFC2616 - editorial - active |
|
||
i41 | Security Considerations | RFC2616 - design - active |
|
||
i42 | RFC2606 compliance | RFC2616 - editorial - closed |
i43 | Fragment combination / precedence during redirects | RFC2616 - design - active |
|
||
i44 | Unneeded references | RFC2616 - editorial - closed |
i45 | RFC977 reference | RFC2616 - editorial - closed |
i46 | references to RFC1700 | RFC2616 - editorial - closed |
|
||
i47 | inconsistency in date format explanation | RFC2616 - editorial - closed |
|
||
i48 | Date reference typo | RFC2616 - editorial - closed |
|
||
i49 | Connection header text | RFC2616 - editorial - closed |
|
||
i50 | Misc. Typos | RFC2616 - editorial - active |
|
||
i51 | HTTP-date vs. rfc1123-date | RFC2616 - design - active |
|
||
i52 | Sort 1.3 Terminology | RFC2616 - editorial - active |
|
||
i53 | Allow is not in 13.5.2 | RFC2616 - editorial - active |
|
||
i54 | Definition of 1xx Warn-Codes | RFC2616 - design - active |
|
||
i55 | Updating to RFC4288 | RFC2616 - editorial - active |
|
||
i56 | 6.1.1 can be misread as a complete list | RFC2616 - editorial - active |
|
||
i57 | Status Code and Reason Phrase | RFC2616 - editorial - active |
|
||
i58 | What identifies an HTTP resource | RFC2616 - design - active |
|
||
i59 | Status Code Registry | RFC2616 - editorial - active |
|
||
i60 | 13.5.1 and 13.5.2 | RFC2616 - editorial - active |
|
||
i61 | Redirection vs. Location | RFC2616 - design - active |
|
||
i62 | Whitespace in quoted-pair | RFC2616 - design - closed |
|
||
i63 | Header length limit with encoded words | RFC2616 - design - active |
|
||
i64 | WS in quoted-pair | RFC2616 - design - active |
|
||
i65 | Informative references | RFC2616 - editorial - closed |
|
||
i66 | ISO-8859-1 Reference | RFC2616 - editorial - closed |
|
||
i67 | Quoting Charsets | RFC2616 - editorial - active |
|
||
i68 | Encoding References Normative | RFC2616 - editorial - closed |
|
||
i69 | Clarify "Requested Variant" | RFC2616 - design - active |
|
||
i70 | Cacheability of 303 response | RFC2616 - design - active |
|
||
i71 | Examples for ETag matching | RFC2616 - design - active |
|
||
i72 | Request Method Registry | RFC2616 - editorial - active |
|
||
i73 | Clarification of the term "deflate" | RFC2616 - design - active |
|
||
i74 | Character encodings for Headers | RFC2616 - design - active |
|
||
i75 | RFC2145 Normative | RFC2616 - design - active |
|
||
i76 | Deprecate 305 Use Proxy | RFC2616 - design - active |
|
||
i77 | Line folding | RFC2616 - design - active |
|
||
i78 | Relationship between 401, Authorization and WWW-Authenticate | RFC2616 - design - active |
|
||
i79 | Content-* vs. PUT | RFC2616 - design - active |
|
||
i80 | Content-Location isn't special | RFC2616 - design - active |
|
||
i81 | Content Negotiation for media types | RFC2616 - design - active |
|
||
i82 | rel_path not used | RFC2616 - editorial - active |
|
||
i83 | OPTIONS * and proxies | RFC2616 - design - active |
|
||
i84 | Redundant cross-references | RFC2616 - editorial - closed |
|
||
i85 | Custom Ranges | RFC2616 - design - active |
|
||
i86 | Normative up-to-date references | RFC2616 - editorial - closed |
|
||
i87 | typo in 13.2.2 | RFC2616 - editorial - closed |
i88 | 205 Bodies | RFC2616 - design - active |
|
||
i89 | If-* and entities | RFC2616 - design - active |
|
||
i90 | Delimiting messages with multipart/byteranges | RFC2616 - design - active |
|
||
i91 | Duplicate Host header requirements | RFC2616 - editorial - active |
|
||
i92 | Empty Host Headers - BNF | RFC2616 - editorial - active |
|
||
i93 | Repeating single-value headers | RFC2616 - design - active |
|
||
i94 | Reason-Phrase BNF | RFC2616 - design - active |
|