Header compression question
Issue #154: Sending a response before the request is complete
[#153] PUSH_PROMISE headers
HTTP Layer rework and PUSH_PROMISE contents
HTTP Mapping editorial changes
Header compression, editorial
[#150] Making certain settings mandatory
- Re: [#150] Making certain settings mandatory
draft-snell-httpbis-mget: Proposal for a new SHORTER format to header field :path
ADMIN: Discussion on Github issues
Ranges
Brief header compression comments
I-D Action: draft-ietf-httpbis-header-compression-00.txt
Outcomes of the SF Interim Meeting
Rough Minutes from SF F2F
Fwd: Summer of Code project
Out-of-order Frames
Is the ability to disable flow control really needed?
- Re: Is the ability to disable flow control really needed?
- Re: Is the ability to disable flow control really needed?
- Re: Is the ability to disable flow control really needed?
- Re: Is the ability to disable flow control really needed?
- Re: Is the ability to disable flow control really needed?
- Re: Is the ability to disable flow control really needed?
- Re: Is the ability to disable flow control really needed?
- Re: Is the ability to disable flow control really needed?
- Re: Is the ability to disable flow control really needed?
- RE: Is the ability to disable flow control really needed?
- Re: Is the ability to disable flow control really needed?
- Re: Is the ability to disable flow control really needed?
- Re: Is the ability to disable flow control really needed?
- Re: Is the ability to disable flow control really needed?
- Re: Is the ability to disable flow control really needed?
- Re: Is the ability to disable flow control really needed?
- Re: Is the ability to disable flow control really needed?
#487 Resubmission of 403
DASH/XMPP workshop
Questions on Frame Size
END_STREAM on PUSH_PROMISE
Design: Adding ASSOCIATED_ONLY
- Re: Design: Adding ASSOCIATED_ONLY
- Re: Design: Adding ASSOCIATED_ONLY
Fwd: Nit: Server-sent priority
Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR
- Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR
- Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR
- Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR
- Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR
- Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR
- Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR
- Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR
- Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR
- Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR
- Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR
- Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR
- Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR
- Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR
- Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR
- Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR
- Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR
- Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR
- Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR
- Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR
Nit: Server-sent priority
GOAWAY(AND_DONT_COME_BACK)
Multiple Headers
Issue re. HTTP2 STREAM and HEADER block use same end bit polarity
- Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity
- Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity
- Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity
- Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity
- Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity
- Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity
- Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity
- Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity
- Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity
- Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity
- Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity
- Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity
- Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity
- Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity
- Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity
- Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity
- Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity
- Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity
- Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity
- Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity
- Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity
Re: PUT, If-Match, 412 - over-constrained?
Re: [saag] Is the CA market broken?
Is the CA market broken?
Until HTTP header when the representation will disappear in the future
duplicate parameters
p6: Warning header field
port #?
Fwd: New Version Notification for draft-snell-httpbis-bohe-09.txt
draft-snell-http-prefer: Preference-Applied
Header Compression
HTTP URI in the form of "http://example.com?query"
- Re: HTTP URI in the form of "http://example.com?query"
Questions on Server Push
Agenda for June Interim meeting
I-D Action: draft-ietf-httpbis-http2-03.txt
HTTP in JSON Binary Encoding / Data Model
WGLC p1: Scope of https update
Proposal - Reduce HTTP2 frame length from 16 to 12 bits
- Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits
- Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits
- Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits
- Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits
- Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits
- Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits
- Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits
- Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits
- Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits
- Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits
- Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits
- Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits
- Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits
- Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits
- Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits
- Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits
- Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits
- Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits
- Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits
- Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits
- Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits
- Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits
- Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits
- Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits
HTTP/2.0 SETTINGS frame values
obs-text character encoding and error handling; duplicate parameter names in Content-Type
http2 draft feedback on flow control
Design Issue: GZIP flag on DATA Frames
- Re: Design Issue: GZIP flag on DATA Frames
- Re: Design Issue: GZIP flag on DATA Frames
- Re: Design Issue: GZIP flag on DATA Frames
- Re: Design Issue: GZIP flag on DATA Frames
- Re: Design Issue: GZIP flag on DATA Frames
- Re: Design Issue: GZIP flag on DATA Frames
- Re: Design Issue: GZIP flag on DATA Frames
Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
- Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY
notes on http2 draft
Fwd: New Version Notification for draft-snell-httpbis-ext-frames-00.txt
Fwd: New Version Notification for draft-snell-httpbis-bohe-08.txt
Preliminary agenda for the SF Interim
adding Header Continuation
"Magic" string
Re: Lingering Close
Re: Caching 412 responses
HTTPBIS WG Interim Meeting, August 5-7, 2013
Part 2: Editorial changes involving "instance of time"
Implementation Notes on Server Push
- Re: Implementation Notes on Server Push
- Re: Implementation Notes on Server Push
- Re: Implementation Notes on Server Push
- Re: Implementation Notes on Server Push
How to pronounce "charset"?
- Re: How to pronounce "charset"?
- Re: How to pronounce "charset"?
- Re: How to pronounce "charset"?
- Re: How to pronounce "charset"?
http/2 test framework
Re: [http-auth] Associating URI-based identities with HTTP requests
Design: Frame type extensibility issues
Design: Ignored Unknown Frame Types and Intermediaries
- Re: Design: Ignored Unknown Frame Types and Intermediaries
- Re: Design: Ignored Unknown Frame Types and Intermediaries
- Re: Design: Ignored Unknown Frame Types and Intermediaries
- Re: Design: Ignored Unknown Frame Types and Intermediaries
- Re: Design: Ignored Unknown Frame Types and Intermediaries
- Re: Design: Ignored Unknown Frame Types and Intermediaries
- Re: Design: Ignored Unknown Frame Types and Intermediaries
- Re: Design: Ignored Unknown Frame Types and Intermediaries
- Re: Design: Ignored Unknown Frame Types and Intermediaries
- Re: Design: Ignored Unknown Frame Types and Intermediaries
- Re: Design: Ignored Unknown Frame Types and Intermediaries
- Re: Design: Ignored Unknown Frame Types and Intermediaries
- Re: Design: Ignored Unknown Frame Types and Intermediaries
- Re: Design: Ignored Unknown Frame Types and Intermediaries
- Re: Design: Ignored Unknown Frame Types and Intermediaries
- Re: Design: Ignored Unknown Frame Types and Intermediaries
- Re: Design: Ignored Unknown Frame Types and Intermediaries
- Re: Design: Ignored Unknown Frame Types and Intermediaries
- Re: Design: Ignored Unknown Frame Types and Intermediaries
- Re: Design: Ignored Unknown Frame Types and Intermediaries
Associating URI-based identities with HTTP requests
Design Issue: Overlong Frames
3.5.1 Connection Error Handling
p2: section 5.3.2 (Accept header)
Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)
- Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)
- Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)
- Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)
- Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)
- Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)
- Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)
- Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)
- Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)
- Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)
- Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)
- Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)
- Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)
- Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)
- Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)
- Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)
- Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)
- Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)
- Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)
- Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)
- Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)
- Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)
- Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)
- Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items)
redundancy with WINDOW_UPDATE and SETTINGS_FLOW_CONTROL_OPTIONS
http://http2.github.io/http2-spec/#rfc.section.3.1 connections
http://http2.github.io/http2-spec/#FrameHeader section on Flags being unset
Requiring proxies to process warn-date
Design Issue: Frame Size Items
- RE: Design Issue: Frame Size Items
- Re: Design Issue: Frame Size Items
- Re: Design Issue: Frame Size Items
#469: definition of "private"
#440: max of max-age
Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type
- Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type
- Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type
- Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type
- Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type
- Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type
- Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type
http/2 initial limits - i see flow control initial limits specified, but not stream limits
- Re: http/2 initial limits - i see flow control initial limits specified, but not stream limits
Design Issue: Can we go ahead and remove persistent settings?
Design Issue: Life-cycle of a Stream
- Re: Design Issue: Life-cycle of a Stream
- Re: Design Issue: Life-cycle of a Stream
- Re: Design Issue: Life-cycle of a Stream
WGLC p1: proxy handling of a really bad Content-Length
- Re: WGLC p1: proxy handling of a really bad Content-Length
- Re: WGLC p1: proxy handling of a really bad Content-Length
WGLC p1: MUST fix Content-Length?
WGLC: p7 MUSTs
WGLC: p6 MUSTs
WGLC: p5 MUSTs
WGLC: p4 MUSTs
WGLC: p2 MUSTs
WGLC: p1 MUSTs
- Re: WGLC: p1 MUSTs
WGLC: SHOULD and conformance
WGLC: Strengthening SHOULDs
WGLC: misused SHOULDs
p7: forwarding Proxy-*
WGLC p1: Tear-down
WGLC p1: Persistence & 1.1 proxies
WGLC p7: Parsing auth challenges
WGLC p1: Delimiting messages with multipart/byteranges
- Re: WGLC p1: Delimiting messages with multipart/byteranges
- Re: WGLC p1: Delimiting messages with multipart/byteranges
Request: Have git commit messages for design changes include links to relevant discussion email threads
- Re: Request: Have git commit messages for design changes include links to relevant discussion email threads
- Re: Request: Have git commit messages for design changes include links to relevant discussion email threads
p2 / p6: What is "cacheable"?
p2: deprecating 205 Reset Content?
p6: Vary and effects on future requests
Editorial notes on p6
For review: editorial updates pull request
Editorial Issue: Persisted Settings... when does the client need to return them?
- Re: Editorial Issue: Persisted Settings... when does the client need to return them?
Editorial Issue: Unknown/Undefined Settings IDs
Design Issue: HEADERS+PRIORITY "MUST be used" for each stream that is created??
- Re: Design Issue: HEADERS+PRIORITY "MUST be used" for each stream that is created??
Design Issue: Which frames are allowed to reference Stream ID #0 and which aren't?
Design Issue: Unknown Frame Type MUST IGNORE rule and Denial of Service Attacks
- RE: Design Issue: Unknown Frame Type MUST IGNORE rule and Denial of Service Attacks
Design Issue: Must Ignore Rule for Unknown Frame Types
Design Issue: Frame Processing Model
RST_STREAM and FINAL flag
Design Issue: PUSH_PROMISE and Stream Priority
- Re: Design Issue: PUSH_PROMISE and Stream Priority
- Re: Design Issue: PUSH_PROMISE and Stream Priority
- Re: Design Issue: PUSH_PROMISE and Stream Priority
- RE: Design Issue: PUSH_PROMISE and Stream Priority
- Re: Design Issue: PUSH_PROMISE and Stream Priority
- Re: Design Issue: PUSH_PROMISE and Stream Priority
- Re: Design Issue: PUSH_PROMISE and Stream Priority
- Re: Design Issue: PUSH_PROMISE and Stream Priority
- Re: Design Issue: PUSH_PROMISE and Stream Priority
- Re: Design Issue: PUSH_PROMISE and Stream Priority
- Re: Design Issue: PUSH_PROMISE and Stream Priority
- Re: Design Issue: PUSH_PROMISE and Stream Priority
- Re: Design Issue: PUSH_PROMISE and Stream Priority
- Re: Design Issue: PUSH_PROMISE and Stream Priority
- RE: Design Issue: PUSH_PROMISE and Stream Priority
- Re: Design Issue: PUSH_PROMISE and Stream Priority
- Re: Design Issue: PUSH_PROMISE and Stream Priority
Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
- Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams
FYI.. merged pull request..
Editorial Issue: Uniteral Stream Creation
Editorial Issues: Section 4.2.2
HTTP Request+Response issues
Push Promise Issues
Re: Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication
- Re: Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication
- Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
- Re: Comments on Explicit/Trusted Proxy
p2: Considerations for new headers
what's up with commenting on http/2 github issues
- Re: what's up with commenting on http/2 github issues
- Re: what's up with commenting on http/2 github issues
p2: Expect: 100-continue and "final" status codes
- Re: p2: Expect: 100-continue and "final" status codes
- Re: p2: Expect: 100-continue and "final" status codes
- Re: p2: Expect: 100-continue and "final" status codes
- Re: p2: Expect: 100-continue and "final" status codes
- Re: p2: Expect: 100-continue and "final" status codes
- Re: p2: Expect: 100-continue and "final" status codes
- Re: p2: Expect: 100-continue and "final" status codes
- Re: p2: Expect: 100-continue and "final" status codes
- #467: Expect: 100-continue and "final" status codes
- Re: #467: Expect: 100-continue and "final" status codes
- Re: #467: Expect: 100-continue and "final" status codes
- Re: #467: Expect: 100-continue and "final" status codes
- Re: #467: Expect: 100-continue and "final" status codes
- Re: Expect: 100-continue and "final" status codes
- Re: p2: Expect: 100-continue and "final" status codes
p2: Expectation extensions
p2: editorial for Expect and 1xx
Re: WGLC: p6 editorial nits
p1: additional security considerations
p1/p2: 203 Non-Authoritative Information
p7: editorial suggestions
p5: editorial suggestions
p4: editorial suggestions
- #461, was: p4: editorial suggestions
Updated Link I-D
Re: draft-ietf-httpbis-p2-semantics section 3.1.3.1 confusion
Git Issues: Reserved Stream-ID Bit
Git Issues: PING
Updated I-D..
p2: scope for status codes
p2: Requirements upon proxies for Expect
p2: Accept-Language missing, empty or no match
- Re: p2: Accept-Language missing, empty or no match
- Re: p2: Accept-Language missing, empty or no match
- Re: p2: Accept-Language missing, empty or no match
- Re: p2: Accept-Language missing, empty or no match
- Re: p2: Accept-Language missing, empty or no match
p2: Content-Length in HEAD responses
- Re: p2: Content-Length in HEAD responses
- Re: p2: Content-Length in HEAD responses
- Re: p2: Content-Length in HEAD responses
p2: Purely editorial feedback
- Re: p2: Purely editorial feedback
- Re: p2: Purely editorial feedback
- Re: p2: Purely editorial feedback
- Re: p2: Purely editorial feedback
p1: transfer coding registry
p1: Upgrade ordering (possible HTTP/2 impact)
- Re: p1: Upgrade ordering (possible HTTP/2 impact)
- Re: p1: Upgrade ordering (possible HTTP/2 impact)
- Re: p1: Upgrade ordering (possible HTTP/2 impact)
- Re: p1: Upgrade ordering (possible HTTP/2 impact)
- Re: p1: Upgrade ordering (possible HTTP/2 impact)
- Re: p1: Upgrade ordering (possible HTTP/2 impact)
- Re: p1: Upgrade ordering (possible HTTP/2 impact)
- Re: p1: Upgrade ordering (possible HTTP/2 impact)
- Re: p1: Upgrade ordering (possible HTTP/2 impact)
- Re: p1: Upgrade ordering (possible HTTP/2 impact)
- Re: p1: Upgrade ordering (possible HTTP/2 impact)
- Re: p1: Upgrade ordering (possible HTTP/2 impact)
- Re: p1: Upgrade ordering (possible HTTP/2 impact)
- Re: p1: Upgrade ordering (possible HTTP/2 impact)
- Re: p1: Upgrade ordering (possible HTTP/2 impact)
- Re: p1: Upgrade ordering (possible HTTP/2 impact)
- Re: p1: Upgrade ordering (possible HTTP/2 impact)
- Re: p1: Upgrade ordering (possible HTTP/2 impact)
- Re: p1: Upgrade ordering (possible HTTP/2 impact)
p1: generating "internal" errors
p1: handling obs-fold
p1: HTTP and TCP name delegation
p1: HTTP(S) URIs and fragment identifiers
p1: Receiving a higher minor HTTP version number
- Re: p1: Receiving a higher minor HTTP version number
- Re: p1: Receiving a higher minor HTTP version number
p1: Via and gateways
p1: Purely Editorial Feedback
HTTPBIS WG Interim Meeting, June 13-14, 2013
Resumable Uploads
- Re: Resumable Uploads
p1: BWS
p1: whitespace in request-target
- Re: p1: whitespace in request-target
- Re: p1: whitespace in request-target
- #443: p1: whitespace in request-target
Web Keys and HTTP Signatures
- Re: Web Keys and HTTP Signatures
HTTP/2.0 section 2.4 "Starting HTTP/2.0 with Prior Knowledge"
Quoting email (was: HTTP/2 and TCP CWND)
WGLC: p4, 304 Not Modified
Question on Multiplicity of Authorization and WWW-Authenticate
- Re: Question on Multiplicity of Authorization and WWW-Authenticate
- Re: Question on Multiplicity of Authorization and WWW-Authenticate
Status code 451 adoption
Re: Planning for Future Meetings
FYI: Header Compression
HTTP 2.0 "Upgrade" flow
- Re: HTTP 2.0 "Upgrade" flow
- Re: HTTP 2.0 "Upgrade" flow
Header Serialization Discussion
- RE: Header Serialization Discussion
- Re: Header Serialization Discussion
- Re: Header Serialization Discussion
- Re: Header Serialization Discussion
- Re: Header Serialization Discussion
3.3.1 Frame Header: Purpose of 1-bit reserved field?
Updated Delta+BOHE Impl in Java
Transitioning to TLS Application Layer Protocol Negotiation (ALPN)
RE: HeaderDiff specification
Compression analysis of perfect atom-based compressor
- Re: Compression analysis of perfect atom-based compressor
- RE: Compression analysis of perfect atom-based compressor
- Re: Compression analysis of perfect atom-based compressor
WGLC: p5 multiple Range headers
I-D Action: draft-ietf-httpbis-http2-02.txt
HTTP/2 and TCP CWND
- Re: HTTP/2 and TCP CWND
- Re: HTTP/2 and TCP CWND
- Re: HTTP/2 and TCP CWND
- Re: HTTP/2 and TCP CWND
- Re: HTTP/2 and TCP CWND