ietf-http-wg@w3.org from April to June 2019 by subject

"entity" reference in httpbis-semantics

"Fragment" request header

[Anima] Content-Transfer-Encoding and HTTP 1.x in ANIMA BRSKI

[art] Request for well-known URI: matrix

[Editorial Errata Reported] RFC7725 (5512)

[Errata Rejected] RFC7230 (5599)

[Errata Rejected] RFC7230 (5623)

[Ietf-message-headers] Requesting provisional registration for AMP-Cache-Transform header

[Technical Errata Reported] RFC7725 (5181)

[Technical Errata Reported] RFC8586 (5704)

ABNFs out of RFCs, was: Structured Headers: URI type (#782)

Activity Identifiers - Draft Submission

Allow float values for Prefer: wait=<val> (rfc7240)

Are Alt-Svc and Alt-Used headers "hop-by-hop"?

Call for Adoption: draft-polli-resource-digests-http-00

Call For Adoption: HTTP/2 and TLS 1.3 post-handshake authentication

Call for Adoption: Proxy Status

Client Hints and Fingerprinting

Consistency in Stream Beginnings in HTTP/3

Content-Transfer-Encoding and HTTP 1.x in ANIMA BRSKI

cross-site | Re: Formalizing the HTTP State Tokens proposal.

delivery=same-origin | Re: Formalizing the HTTP State Tokens proposal.

DRAFT minutes from IETF104 Prague

Empty lists in Structured Headers (#781)

exposing certificate information (current + upcoming)

Feedback sought on timezone header for HTTP

Few proposal seem to have not attract any attention from the working groups.

Formalizing the HTTP State Tokens proposal.

Fwd: New Version Notification for draft-polli-resource-digests-http-00.txt

HTTP Partial POST Replay

HTTP Testing Resources

HTTP/2 and TLS 1.3 post-handshake authenication

HTTP/2 Server Push and solid compression

HTTP/3 Prioritization Proposal

I-D Action: draft-ietf-httpbis-header-structure-10.txt

I-D Action: draft-ietf-httpbis-http2-secondary-certs-04.txt

I-D Action: draft-ietf-httpbis-http2-tls13-00.txt

I-D Action: draft-ietf-httpbis-proxy-status-00.txt

I-D Action: draft-ietf-httpbis-rfc6265bis-03.txt

Incremental improvements to cookies.

Is CONNECT hop-by-hop?

key, register | Re: Formalizing the HTTP State Tokens proposal.

Migrating some high-entropy HTTP headers to Client Hints.

NEW PREFERENCE - location

Proposal for new header field: SESSION_FORWARD_IDENTITY

Proposal of Generic ReponseForwardHeaders - Can be used for new

Question regarding RFC 8441

Required Domain proposal for Additional Certificates

RFC 8586 on Loop Detection in Content Delivery Networks (CDNs)

same-site |Re: Formalizing the HTTP State Tokens proposal.

Server/Site opt-in #2 | Re: Formalizing the HTTP State Tokens proposal.

Server/Site opt-in | Re: Formalizing the HTTP State Tokens proposal.

Signature #2: No CBOR | Re: Formalizing the HTTP State Tokens proposal.

Signature | Re: Formalizing the HTTP State Tokens proposal.

Status code 422 in http-core uses the term `entity`. Should we use `representation` ?

Structured Headers: URI type (#782)

Testing email to the group!

Testing emailing to the mailing list once again

Updating Digest header RFC3230 using "selected representation"

Weekly github digest (HTTP Working Group Specifications)

What are the semantics of a client sent GOAWAY?

Last message date: Sunday, 30 June 2019 00:45:49 UTC