#19 |
Bodies on GET (and other) requests
|
|
design
|
normal
|
02
|
p1-messaging
|
#20 |
Default charsets for text media types
|
fielding@…
|
design
|
normal
|
14
|
p3-payload
|
#22 |
ETag (and other metadata) in status messages
|
fielding@…
|
design
|
normal
|
22
|
p2-semantics
|
#27 |
Idempotency
|
|
editorial
|
normal
|
unassigned
|
p2-semantics
|
#28 |
Connection closing
|
julian.reschke@…
|
editorial
|
normal
|
11
|
p1-messaging
|
#29 |
Age calculation
|
julian.reschke@…
|
design
|
normal
|
10
|
p6-cache
|
#33 |
TRACE security considerations
|
|
editorial
|
normal
|
unassigned
|
p2-semantics
|
#36 |
ABNF Update
|
julian.reschke@…
|
editorial
|
normal
|
06
|
non-specific
|
#37 |
Vary and non-existant headers
|
|
design
|
normal
|
unassigned
|
p6-cache
|
#38 |
Mismatch Vary
|
|
design
|
normal
|
15
|
p6-cache
|
#39 |
ETag uniqueness
|
julian.reschke@…
|
editorial
|
normal
|
10
|
p4-conditional
|
#54 |
Definition of 1xx Warn-Codes
|
|
design
|
normal
|
08
|
p6-cache
|
#58 |
What identifies an HTTP resource
|
|
editorial
|
normal
|
unassigned
|
p1-messaging
|
#60 |
Placement of 13.5.1 and 13.5.2
|
julian.reschke@…
|
editorial
|
normal
|
10
|
non-specific
|
#73 |
Clarification of the term "deflate"
|
julian.reschke@…
|
design
|
normal
|
10
|
p1-messaging
|
#79 |
Content-* vs. PUT
|
fielding@…
|
design
|
normal
|
13
|
p2-semantics
|
#81 |
Content Negotiation for media types
|
|
design
|
normal
|
09
|
p3-payload
|
#83 |
OPTIONS * and proxies
|
|
design
|
normal
|
10
|
p1-messaging
|
#85 |
Custom Ranges
|
julian.reschke@…
|
design
|
normal
|
11
|
p5-range
|
#86 |
Normative up-to-date references
|
julian.reschke@…
|
editorial
|
normal
|
01
|
non-specific
|
#91 |
Duplicate Host header requirements
|
fielding@…
|
editorial
|
normal
|
02
|
non-specific
|
#93 |
Repeating single-value header fields
|
fielding@…
|
editorial
|
normal
|
unassigned
|
p1-messaging
|
#95 |
Handling multiple Content-Length header fields
|
mnot@…
|
design
|
normal
|
14
|
p1-messaging
|
#105 |
Classification for Allow header field
|
julian.reschke@…
|
design
|
normal
|
03
|
p2-semantics
|
#108 |
Monitoring connections
|
|
editorial
|
normal
|
11
|
p1-messaging
|
#115 |
missing default for qvalue in description of Accept-Encoding
|
julian.reschke@…
|
editorial
|
normal
|
unassigned
|
p3-payload
|
#118 |
Join "Differences Between HTTP Entities and RFC 2045 Entities"?
|
|
editorial
|
normal
|
06
|
p1-messaging
|
#119 |
Description of CONNECT should refer to RFC2817
|
julian.reschke@…
|
editorial
|
normal
|
04
|
p2-semantics
|
#120 |
need new URL for PAD1995 reference
|
|
editorial
|
normal
|
unassigned
|
p1-messaging
|
#121 |
RFC 1806 has been replaced by RFC2183
|
julian.reschke@…
|
editorial
|
normal
|
04
|
p3-payload
|
#122 |
MIME-Version not listed in P1, general header fields
|
julian.reschke@…
|
editorial
|
normal
|
11
|
p3-payload
|
#123 |
Factor out Content-Disposition
|
julian.reschke@…
|
design
|
normal
|
12
|
p3-payload
|
#129 |
List-type header fields vs Set-Cookie
|
|
design
|
normal
|
unassigned
|
p1-messaging
|
#130 |
introduction to part 7 is work-in-progress
|
julian.reschke@…
|
editorial
|
normal
|
12
|
p7-auth
|
#134 |
RFC822 reference left in discussion of date formats
|
|
editorial
|
normal
|
06
|
p1-messaging
|
#139 |
Methods and Caching
|
mnot@…
|
design
|
normal
|
11
|
p2-semantics
|
#140 |
update note citing RFC 1945 and 2068
|
julian.reschke@…
|
editorial
|
normal
|
08
|
p2-semantics
|
#141 |
should we have an auth scheme registry
|
julian.reschke@…
|
design
|
normal
|
12
|
p7-auth
|
#142 |
State base for *-byte-pos and suffix-length
|
julian.reschke@…
|
editorial
|
normal
|
06
|
p5-range
|
#147 |
serving negotiated responses from cache: header-specific canonicalization
|
mnot@…
|
design
|
normal
|
unassigned
|
p6-cache
|
#151 |
range unit missing from other-ranges-specifier in Range header
|
ylafon@…
|
editorial
|
normal
|
unassigned
|
p5-range
|
#153 |
case-sensitivity of etag weakness indicator
|
julian.reschke@…
|
editorial
|
normal
|
07
|
p4-conditional
|
#154 |
Content-Location base-setting problems
|
mnot@…
|
design
|
normal
|
unassigned
|
p3-payload
|
#156 |
Isolate TCP-specific aspects of HTTP
|
|
editorial
|
normal
|
unassigned
|
p1-messaging
|
#157 |
IP addresses in URLs
|
fielding@…
|
editorial
|
normal
|
unassigned
|
p1-messaging
|
#158 |
Keep-Alive and Proxy-Connection headers
|
mnot@…
|
design
|
normal
|
18
|
p1-messaging
|
#161 |
base for numeric protocol elements
|
julian.reschke@…
|
editorial
|
normal
|
unassigned
|
non-specific
|
#162 |
comment ABNF
|
julian.reschke@…
|
design
|
normal
|
07
|
p1-messaging
|
#164 |
status codes vs methods
|
|
editorial
|
normal
|
unassigned
|
p2-semantics
|
#167 |
Content-Location on 304 responses
|
mnot@…
|
design
|
normal
|
unassigned
|
p6-cache
|
#168 |
Clarify differences between / requirements for request and response CC directives
|
julian.reschke@…
|
editorial
|
normal
|
10
|
p6-cache
|
#169 |
private and no-cache CC directives with headers
|
mnot@…
|
design
|
normal
|
08
|
p6-cache
|
#170 |
Do not require "updates" relation for specs that register status codes or method names
|
|
design
|
normal
|
07
|
p2-semantics
|
#171 |
Are OPTIONS and TRACE safe?
|
julian.reschke@…
|
design
|
normal
|
11
|
p2-semantics
|
#172 |
take over HTTP Upgrade Token Registry
|
|
design
|
normal
|
unassigned
|
p1-messaging
|
#174 |
Caching authenticated responses
|
|
design
|
normal
|
10
|
p6-cache
|
#177 |
Realm required on challenges
|
julian.reschke@…
|
design
|
normal
|
16
|
p7-auth
|
#178 |
Content-MD5 and partial responses
|
julian.reschke@…
|
design
|
normal
|
14
|
p3-payload
|
#180 |
Note special status of Content-* prefix in header field registration procedures
|
|
editorial
|
normal
|
11
|
non-specific
|
#181 |
Accept-Language: which RFC4647 filtering?
|
|
design
|
normal
|
09
|
p3-payload
|
#183 |
"requested resource" in content-encoding definition
|
julian.reschke@…
|
design
|
normal
|
11
|
p3-payload
|
#185 |
Location header field payload handling
|
mnot@…
|
design
|
normal
|
18
|
p2-semantics
|
#187 |
RFC2047 and warn-text
|
julian.reschke@…
|
design
|
normal
|
08
|
p6-cache
|
#189 |
move definitions of gzip/deflate/compress to part 1
|
julian.reschke@…
|
editorial
|
normal
|
08
|
non-specific
|
#190 |
OPTIONS vs Max-Forwards
|
|
editorial
|
normal
|
unassigned
|
p2-semantics
|
#191 |
Location header field ABNF should use "URI"
|
|
editorial
|
normal
|
08
|
p2-semantics
|
#193 |
Trailer requirements
|
|
design
|
normal
|
12
|
p1-messaging
|
#194 |
disallow control characters in quoted-pair
|
|
design
|
normal
|
unassigned
|
p1-messaging
|
#195 |
auth-param syntax
|
julian.reschke@…
|
design
|
normal
|
16
|
p7-auth
|
#197 |
Effect of CC directives on history lists
|
|
design
|
normal
|
09
|
p6-cache
|
#198 |
move IANA registrations for optional status codes
|
julian.reschke@…
|
editorial
|
normal
|
08
|
non-specific
|
#199 |
Status codes and caching
|
mnot@…
|
design
|
normal
|
11
|
non-specific
|
#201 |
header parsing, treatment of leading and trailing OWS
|
julian.reschke@…
|
editorial
|
normal
|
10
|
p1-messaging
|
#203 |
Max-Forwards vs extension methods
|
julian.reschke@…
|
design
|
normal
|
13
|
p2-semantics
|
#204 |
Text about clock requirement for caches belongs in p6
|
mnot@…
|
editorial
|
normal
|
unassigned
|
p1-messaging
|
#208 |
IANA registry for cache-control directives
|
julian.reschke@…
|
design
|
normal
|
10
|
p6-cache
|
#209 |
identified resource indepent of scheme?
|
fielding@…
|
editorial
|
normal
|
unassigned
|
p1-messaging
|
#211 |
Heuristic caching of URLs with query components
|
julian.reschke@…
|
design
|
normal
|
10
|
p6-cache
|
#213 |
What is the value space of HTTP status codes?
|
|
design
|
normal
|
13
|
p1-messaging
|
#216 |
No-cache definition
|
|
design
|
normal
|
11
|
p6-cache
|
#217 |
Caches can't be required to serve ranges
|
ylafon@…
|
design
|
normal
|
12
|
p5-range
|
#218 |
Explain non-HTTP URIs in HTTP
|
|
design
|
normal
|
20
|
p1-messaging
|
#220 |
consider removing the "changes from 2068" sections
|
julian.reschke@…
|
editorial
|
normal
|
11
|
non-specific
|
#221 |
effective request URI: handling of missing host in HTTP/1.0
|
|
design
|
normal
|
unassigned
|
p1-messaging
|
#222 |
effective request URI: handling of request-target *
|
fielding@…
|
design
|
normal
|
19
|
p1-messaging
|
#223 |
Allowing heuristic caching for new status codes
|
|
design
|
normal
|
22
|
p6-cache
|
#224 |
Header Field Classification
|
|
design
|
normal
|
13
|
non-specific
|
#225 |
PUT side effect: invalidation or just stale?
|
mnot@…
|
design
|
normal
|
15
|
non-specific
|
#227 |
Combining HEAD responses
|
mnot@…
|
design
|
normal
|
19
|
p6-cache
|
#229 |
Considerations for new status codes
|
mnot@…
|
design
|
normal
|
12
|
p2-semantics
|
#230 |
Considerations for new methods
|
mnot@…
|
design
|
normal
|
12
|
p2-semantics
|
#231 |
Considerations for new header fields
|
mnot@…
|
design
|
normal
|
17
|
non-specific
|
#232 |
User-Agent guidelines
|
mnot@…
|
design
|
normal
|
12
|
p2-semantics
|
#233 |
Is * usable as a request-uri for new methods?
|
|
design
|
normal
|
13
|
p2-semantics
|
#235 |
Cache Invalidation only happens upon successful responses
|
mnot@…
|
design
|
normal
|
15
|
p6-cache
|
#237 |
absorbing the auth framework from 2617
|
julian.reschke@…
|
design
|
normal
|
12
|
p7-auth
|
#238 |
Requirements for user intervention during redirects
|
|
design
|
normal
|
19
|
p2-semantics
|
#239 |
Migrate CONNECT from RFC2817 to p2
|
mnot@…
|
design
|
normal
|
13
|
p2-semantics
|
#240 |
Migrate Upgrade details from RFC2817
|
mnot@…
|
design
|
normal
|
13
|
non-specific
|
#241 |
Need to clarify eval order/interaction of conditional headers
|
|
design
|
normal
|
20
|
p4-conditional
|