case-sensitivity of weakness indicator
NEW ISSUE: isolate TCP-specific aspects of HTTP
NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
Pipelining in HTTP 1.1
New mailing list: hybi (HTTP "long poll" and related protocols)
Re: issue 85 - range unit extensions
Re: NEW ISSUE: Drop Content-Location
URI handling for Location
Correct status code for unknown transfer-encoding
Minutes from informal IETF/W3C meeting about HTML5 work
Nit in section 2.1.1 of httpbis-p1
HTTPbis meeting agenda, participation details
p6-caching: commentary from -05 to -06
i58: What identifies an HTTP resource
OAuth and HTTP proxies
I-D Action:draft-ietf-httpbis-p4-conditional-06.txt
I-D Action:draft-ietf-httpbis-p2-semantics-06.txt
I-D Action:draft-ietf-httpbis-p5-range-06.txt
I-D Action:draft-ietf-httpbis-p6-cache-06.txt
I-D Action:draft-ietf-httpbis-p7-auth-06.txt
I-D Action:draft-ietf-httpbis-p1-messaging-06.txt
I-D Action:draft-ietf-httpbis-p3-payload-06.txt
Keep-alive header in RFC2616
required behaviour of client when abortive disconnect
- Re: required behaviour of client when abortive disconnect
- Re: required behaviour of client when abortive disconnect
I-D Action:draft-ietf-httpbis-security-properties-03.txt
HTTPbis status
Re: Cache key history
Coming to a conclusion on draft-abarth-origin
FYI: Link -04
CERT VU#435052 - intercepting proxy vulnerability
Re: Users with different access rights in HTTP Authentication
Fwd: I-D Action:draft-jennings-http-srv-01.txt
Referer URI MUST NOT include a fragment
- Re: Referer URI MUST NOT include a fragment
- RE: Referer URI MUST NOT include a fragment
- Re: Referer URI MUST NOT include a fragment
- Re: Referer URI MUST NOT include a fragment
Empty host in 'http' scheme
Origin vs Authority; use of HTTPS (draft-nottingham-site-meta-01)
- Re: Origin vs Authority; use of HTTPS (draft-nottingham-site-meta-01)
- Re: Origin vs Authority; use of HTTPS (draft-nottingham-site-meta-01)
Extension headers and caching
Re: PROPOSAL - i109: Clarify entity / representation / variant terminology
- Re: PROPOSAL - i109: Clarify entity / representation / variant terminology
- Re: PROPOSAL - i109: Clarify entity / representation / variant terminology
Weak ETag handling
New issue: Clarify when Referer is sent #144
Definition of 'resource' not consistent with RFC 3986
Re: Feedback on draft-nottingham-http-link-header-03, was: Fwd: New Version Notification for draft-nottingham-http-link-header-03
GET/HEAD support "MUST"
PATCH draft
The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- RE: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Origin header for safe methods other than GET/HEAD, was: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
Re: [W3C BPWG] HTTP header fields X-* and normal ones / question
- RE: [W3C BPWG] HTTP header fields X-* and normal ones / question
- Re: [W3C BPWG] HTTP header fields X-* and normal ones / question
A question about Content-Length header
- Re: A question about Content-Length header
- Re: A question about Content-Length header
- Re: A question about Content-Length header
- Re: A question about Content-Length header
Use of Link rel+type for application discovery
- Re: Use of Link rel+type for application discovery
- Re: Use of Link rel+type for application discovery
Two new IDs of relevance to this working group
A question about Content-Length header & Transfer Coding
Review of Content-Encoding: value token
- Re: Review of Content-Encoding: value token
[W3C BPWG] HTTP header fields X-* and normal ones / question
- Re: [W3C BPWG] HTTP header fields X-* and normal ones / question
- Re: [W3C BPWG] HTTP header fields X-* and normal ones / question
Proposal: 3xx (Unauthorized, See Other) status
Status update / San Francisco meeting / etc.
Request for feedback: HTTP-based Resource Descriptor Discovery
Status of RFC 2295: Transparent Content Negotiation in HTTP (Experimental)
Providing two-way communication back to a server from a Web page
- RE: Providing two-way communication back to a server from a Web page
- Re: Providing two-way communication back to a server from a Web page