| 2 |
'unsafe' characters
|
p1-messaging
|
1 |
3 |
| 3 |
Chunk Size Definition
|
p1-messaging
|
1 |
0 |
| 4 |
Message Length
|
p1-messaging
|
1 |
1 |
| 5 |
Via is a MUST
|
p2-semantics
|
1 |
0 |
| 6 |
Fragments allowed in Location
|
p2-semantics
|
1 |
11 |
| 7 |
Editors Notes
|
non-specific |
0 |
1 |
| 8 |
Media Type Registrations
|
non-specific |
2 |
4 |
| 9 |
Trailer
|
p6-cache
|
1 |
1 |
| 11 |
URI includes query
|
p1-messaging
|
1 |
1 |
| 12 |
Invalidation after Update or Delete
|
p6-cache
|
1 |
3 |
| 13 |
Updated reference for language tags
|
p3-payload
|
0 |
28 |
| 14 |
Clarification regarding quoting of charset values
|
p3-payload
|
2 |
29 |
| 15 |
No close on 1xx responses
|
p1-messaging
|
1 |
14 |
| 16 |
Remove 'identity' token references
|
non-specific |
1 |
3 |
| 17 |
Revise description of the POST method
|
p2-semantics
|
1 |
11 |
| 18 |
Cache validators in 206 responses
|
p5-range
|
1 |
3 |
| 19 |
Bodies on GET (and other) requests
|
p2-semantics
|
1 |
72 |
| 20 |
Default charsets for text media types
|
p3-payload
|
5 |
97 |
| 21 |
PUT side effects
|
p2-semantics
|
1 |
10 |
| 22 |
ETag (and other metadata) in status messages
|
p2-semantics
|
0 |
25 |
| 23 |
no-store invalidation
|
p6-cache
|
0 |
18 |
| 24 |
Requiring Allow in 405 responses
|
p2-semantics
|
1 |
48 |
| 25 |
Accept-Encoding BNF
|
p3-payload
|
1 |
3 |
| 26 |
Import query BNF
|
p1-messaging
|
1 |
2 |
| 27 |
PUT Idempotency
|
p2-semantics
|
0 |
11 |
| 29 |
Age calculation
|
p6-cache
|
0 |
1 |
| 30 |
Header LWS
|
p1-messaging
|
0 |
4 |
| 32 |
OPTIONS *
|
p2-semantics
|
0 |
14 |
| 33 |
TRACE security considerations
|
p2-semantics
|
0 |
3 |
| 34 |
Out-of-date reference for URIs
|
p1-messaging
|
0 |
2 |
| 35 |
Normative and Informative references
|
non-specific |
3 |
0 |
| 36 |
ABNF Update
|
non-specific |
23 |
8 |
| 37 |
Vary and non-existant headers
|
p6-cache
|
0 |
86 |
| 38 |
Mismatch Vary
|
p6-cache
|
0 |
58 |
| 39 |
ETag uniqueness
|
p4-conditional
|
0 |
87 |
| 40 |
Header registration
|
p1-messaging
|
3 |
26 |
| 41 |
Security Considerations
|
non-specific |
0 |
1 |
| 42 |
RFC2606 Compliance
|
non-specific |
1 |
0 |
| 43 |
Fragment combination / precedence during redirects
|
p2-semantics
|
0 |
11 |
| 44 |
Unneeded references
|
p7-auth
|
0 |
3 |
| 45 |
RFC977 reference
|
p1-messaging
|
1 |
2 |
| 46 |
RFC1700 references
|
non-specific |
1 |
2 |
| 47 |
inconsistency in date format explanation
|
p1-messaging
|
2 |
6 |
| 48 |
Date reference typo
|
p1-messaging
|
3 |
4 |
| 49 |
Connection header text
|
p6-cache
|
1 |
6 |
| 50 |
Misc. Typos
|
non-specific |
7 |
20 |
| 51 |
HTTP-date vs. rfc1123-date
|
p1-messaging
|
1 |
37 |
| 52 |
Sort 1.3 Terminology
|
non-specific |
0 |
8 |
| 53 |
Allow is not in 13.5.2
|
p1-messaging
|
0 |
7 |
| 54 |
Definition of 1xx Warn-Codes
|
p6-cache
|
0 |
12 |
| 55 |
Updating to RFC4288
|
non-specific |
5 |
1 |
| 56 |
6.1.1 can be misread as a complete list
|
p2-semantics
|
1 |
1 |
| 57 |
Status Code and Reason Phrase
|
p1-messaging
|
3 |
4 |
| 58 |
What identifies an HTTP resource
|
p1-messaging
|
0 |
11 |
| 59 |
Status Code Registry
|
p2-semantics
|
3 |
69 |
| 60 |
Placement of 13.5.1 and 13.5.2
|
p6-cache
|
0 |
1 |
| 61 |
Redirection vs. Location
|
p2-semantics
|
1 |
33 |
| 62 |
Whitespace in quoted-pair
|
p1-messaging
|
0 |
13 |
| 63 |
RFC2047 encoded words
|
p1-messaging
|
0 |
2 |
| 64 |
WS in quoted-pair
|
p1-messaging
|
1 |
42 |
| 65 |
Informative references
|
p7-auth
|
4 |
6 |
| 66 |
ISO-8859-1 Reference
|
p3-payload
|
2 |
3 |
| 67 |
Quoting Charsets
|
p3-payload
|
4 |
33 |
| 68 |
Encoding References Normative
|
p3-payload
|
2 |
6 |
| 69 |
Clarify "Requested Variant"
|
non-specific |
0 |
139 |
| 70 |
Cacheability of 303 response
|
p2-semantics
|
2 |
21 |
| 71 |
Examples for ETag matching
|
p4-conditional
|
1 |
35 |
| 72 |
Request Method Registry
|
p2-semantics
|
10 |
71 |
| 73 |
Clarification of the term "deflate"
|
p3-payload
|
0 |
11 |
| 74 |
Character Encodings in TEXT
|
p1-messaging
|
0 |
325 |
| 75 |
RFC2145 Normative
|
p1-messaging
|
0 |
6 |
| 76 |
305 Use Proxy
|
p2-semantics
|
3 |
23 |
| 77 |
Line folding
|
p1-messaging
|
0 |
57 |
| 78 |
Relationship between 401, Authorization and WWW-Authenticate
|
p7-auth
|
0 |
8 |
| 79 |
Content-* vs. PUT
|
p2-semantics
|
0 |
39 |
| 80 |
Content-Location isn't special
|
p3-payload
|
0 |
17 |
| 81 |
Content Negotiation for media types
|
p3-payload
|
0 |
0 |
| 82 |
rel_path not used
|
p1-messaging
|
1 |
3 |
| 83 |
OPTIONS * and proxies
|
p2-semantics
|
0 |
4 |
| 84 |
Redundant cross-references
|
p2-semantics
|
1 |
2 |
| 85 |
Custom Ranges
|
p5-range
|
0 |
32 |
| 86 |
Normative up-to-date references
|
non-specific |
1 |
1 |
| 87 |
typo in 13.2.2
|
p6-cache
|
1 |
1 |
| 88 |
205 Bodies
|
p1-messaging
|
0 |
8 |
| 89 |
If-* and entities
|
p4-conditional
|
0 |
3 |
| 90 |
Delimiting messages with multipart/byteranges
|
p1-messaging
|
0 |
12 |
| 91 |
Duplicate Host header requirements
|
non-specific |
2 |
12 |
| 93 |
Repeating single-value headers
|
p1-messaging
|
0 |
78 |
| 94 |
Reason-Phrase BNF
|
p1-messaging
|
0 |
15 |
| 95 |
Handling multiple Content-Length headers
|
p1-messaging
|
0 |
3 |
| 96 |
Conditional GET text
|
p2-semantics
|
0 |
1 |
| 97 |
Move registrations and registry information to IANA Considerations
|
p1-messaging
|
4 |
26 |
| 98 |
OPTIONS request bodies
|
p2-semantics
|
1 |
6 |
| 99 |
Pipelined requests
|
p1-messaging
|
0 |
49 |
| 100 |
DNS Spoofing / DNS Binding advice
|
p1-messaging
|
0 |
8 |
| 101 |
Definition of validator weakness
|
p4-conditional
|
0 |
65 |
| 102 |
Understanding Content-* on non-PUT requests
|
p2-semantics
|
0 |
27 |
| 103 |
Content-*
|
p2-semantics
|
1 |
33 |
| 104 |
Header type defaulting
|
non-specific |
0 |
16 |
| 105 |
Classification for Allow header
|
p2-semantics
|
1 |
21 |
| 106 |
Vary header classification
|
p6-cache
|
1 |
50 |
| 107 |
Alignment of LM and ETag validation
|
p4-conditional
|
0 |
48 |
| 108 |
Monitoring connections
|
p1-messaging
|
0 |
20 |
| 109 |
Clarify entity / representation / variant terminology
|
non-specific |
0 |
31 |
| 110 |
Clarify rules for determining what entities a response carries
|
non-specific |
0 |
2 |
| 111 |
Use of TEXT
|
non-specific |
0 |
56 |
| 112 |
PUT - "store under" vs "store at"
|
p2-semantics
|
1 |
4 |
| 113 |
language tag matching (Accept-Language) vs RFC4647
|
p3-payload
|
1 |
69 |
| 114 |
Test ticket
|
non-specific |
0 |
0 |
| 115 |
missing default for qvalue in description of Accept-Encoding
|
p3-payload
|
1 |
28 |
| 116 |
Weak ETags on non-GET requests
|
p4-conditional
|
1 |
25 |
| 117 |
cache invalidation upon update
|
p2-semantics
|
0 |
15 |
| 118 |
Join "Differences Between HTTP Entities and RFC 2045 Entities"?
|
p1-messaging
|
0 |
0 |
| 119 |
Description of CONNECT should refer to RFC2817
|
p2-semantics
|
1 |
3 |
| 120 |
need new URL for PAD1995 reference
|
p1-messaging
|
1 |
0 |
| 121 |
RFC 1806 has been replaced by RFC2183
|
p3-payload
|
1 |
13 |
| 122 |
MIME-Version not listed in P1, general header fields
|
p1-messaging
|
0 |
0 |
| 123 |
Factor out Content-Disposition
|
p3-payload
|
0 |
36 |
| 124 |
"entity value" undefined
|
p4-conditional
|
1 |
6 |
| 125 |
Location Content-Location reference request/response mixup
|
p2-semantics
|
1 |
2 |
| 126 |
bogus 2068 Date header reference
|
p4-conditional
|
1 |
4 |
| 127 |
IANA Considerations: update HTTP URI scheme registration
|
p1-messaging
|
1 |
0 |
| 128 |
Cite HTTPS URI scheme definition
|
p1-messaging
|
2 |
12 |
| 129 |
List-type headers vs Set-Cookie
|
p1-messaging
|
1 |
29 |
| 130 |
introduction to part 7 is work-in-progress
|
p7-auth
|
0 |
0 |
| 131 |
increase connection limit
|
p1-messaging
|
0 |
0 |
| 132 |
RFC 2822 is updated by RFC 5322
|
non-specific |
1 |
0 |
| 133 |
multipart/byteranges minimum number of parts
|
p5-range
|
1 |
26 |