From nobody Sun Jan 3 22:48:15 2016 X-Original-To: http-issues@ietfa.amsl.com Delivered-To: http-issues@ietfa.amsl.com X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.941 X-Spam-Level: X-Spam-Status: No, score=-4.941 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_12=2.059, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham Date: Sun, 03 Jan 2016 22:48:10 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1451890090; bh=DoHqgq2kVLeeWOyQt9nLU8W62lQfEHHnYxLjGb1PPqc=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fccKo9ZviJWQgFaGlkICjFJ+tDtm46QqmPrVdFs3ZTw9sYilIpzkAm2yupQ0xL0PH xapmuix6rNxZqLeAvwjFyvYd+5sC4Yu5udkSlh2QvppfJsEiScv74jH3MhBIqRL7M3 aeH60RTV6yk0ohbhOP1PcjLsaN6SebJu/5uytGF8= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [http-extensions] Avoid ambiguity with "may not" and a "MAY" requirement (#66) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_568a15aab614c_75713f86624ab2bc8111d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mnot X-GitHub-Recipient: httpwg-issues X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: http-issues@ietf.org Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.15 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jan 2016 06:48:14 -0000 ----==_mimepart_568a15aab614c_75713f86624ab2bc8111d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit @timbray, thoughts? I think this is editors' discretion (although historically we do try to avoid using RFC2119 keywords in this manner). --- Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/66#issuecomment-168596578 ----==_mimepart_568a15aab614c_75713f86624ab2bc8111d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@timbray, thoughts? I think this is editors' discretion (although historically we do try to avoid using RFC2119 keywords in this manner).


Reply to this email directly or view it on GitHub.

----==_mimepart_568a15aab614c_75713f86624ab2bc8111d-- From nobody Tue Jan 5 10:42:55 2016 X-Original-To: http-issues@ietfa.amsl.com Delivered-To: http-issues@ietfa.amsl.com X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.941 X-Spam-Level: X-Spam-Status: No, score=-4.941 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_12=2.059, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham Date: Tue, 05 Jan 2016 10:42:52 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1452019372; bh=M52mnPAmgfISriEyQF/IrvmJ3DDIJAjUyNSlQ3OrO6I=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GuMWUmWjTxDepBI9AAdd+9G6qYuCIWt6KmyU292NzSmfyICEaPkuO3JtcwL6KGZRX 4gZQJh7wKwNBQWLo5jzRsR9P2h2Eqera//gPBe85Gmj62vp7rgSnCko7ON3cUcwXda BqLYTNOhgYpIiQQYrC43I5ZrChsFZVQU5q10GedE= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [http-extensions] use RFC 7405 ABNF extension (#131) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_568c0eac26633_6e193f853155729c23378a3"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: reschke X-GitHub-Recipient: httpwg-issues X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: http-issues@ietf.org Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.15 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jan 2016 18:42:55 -0000 ----==_mimepart_568c0eac26633_6e193f853155729c23378a3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Closed #131. --- Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/issues/131#event-506242644 ----==_mimepart_568c0eac26633_6e193f853155729c23378a3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Closed #131.


Reply to this email directly or view it on GitHub.

----==_mimepart_568c0eac26633_6e193f853155729c23378a3-- From nobody Wed Jan 20 18:47:00 2016 X-Original-To: http-issues@ietfa.amsl.com Delivered-To: http-issues@ietfa.amsl.com X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.454 X-Spam-Level: X-Spam-Status: No, score=-5.454 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham Date: Wed, 20 Jan 2016 18:46:56 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1453344417; bh=333PVBzz/zPPq1QhdgviHQaf+aWgEV9/dXS7zBrtoiY=; h=From:Reply-To:To:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=ln/+GxNT6IMEv57MKHnZnqUac1XXmB/kYYRpWbvLTImsP1GvJ+P6bSJBvE8HQyzD0 0/Ez5kdsXAnZTN31fMVsozv/eTvXQ6+4wiHapK/yJLuE2p5zovp+PYtAXi2IidqAwE 8DjEZvfVCyRwd/wxCQYo41PSLbuKY4wptG/kn1f4= To: httpwg/http-extensions Subject: [http-extensions] Altsvc samehost (#134) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_56a046a0ee6d3_5c2c3f8e02e032b81152d8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mnot X-GitHub-Recipient: httpwg-issues X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: http-issues@ietf.org Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.15 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jan 2016 02:46:59 -0000 ----==_mimepart_56a046a0ee6d3_5c2c3f8e02e032b81152d8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit You can view, comment on, or merge this pull request online at: https://github.com/httpwg/http-extensions/pull/134 -- Commit Summary -- * move same-host restriction out of alt-svc * massage "strong authentication" language -- File Changes -- M draft-ietf-httpbis-alt-svc.xml (52) M draft-ietf-httpbis-http2-encryption.md (30) -- Patch Links -- https://github.com/httpwg/http-extensions/pull/134.patch https://github.com/httpwg/http-extensions/pull/134.diff --- Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/134 ----==_mimepart_56a046a0ee6d3_5c2c3f8e02e032b81152d8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

You can view, comment on, or merge this pull request online at:

  https://github.com/httpwg/http-extensions/pull/134

Commit Summary

  • move same-host restriction out of alt-svc
  • massage "strong authentication" language

File Changes

Patch Links:


Reply to this email directly or view it on GitHub.

----==_mimepart_56a046a0ee6d3_5c2c3f8e02e032b81152d8-- From nobody Thu Jan 28 04:33:05 2016 X-Original-To: http-issues@ietfa.amsl.com Delivered-To: http-issues@ietfa.amsl.com X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.908 X-Spam-Level: X-Spam-Status: No, score=-5.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham Date: Thu, 28 Jan 2016 04:33:01 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1453984381; bh=njAuzNNWTH/wWt5TDQVw4MoU0R8ecsWSSyc1ILMpp9k=; h=From:Reply-To:To:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=jyZNeyHg6xB1wriZ+VhQJeAtPvWFPmQv27gR4r2APUa+rZbLOmBQhxTY5dwq3+t8A 5cD/+3Zt8+IEd4z/pGM1pQ+WknxbH8dn24T31pHk+U87xWWIHIc1FuQ7RS11f1UXrW itj0XnpMYZ2BOH8CDNNttb6f6SjXTG5zgzxABAXo= To: httpwg/http-extensions Subject: [http-extensions] encryption-encoding: use two octets to indicate record padding length (#135) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_56aa0a7dcb1f0_46c83faa1b2012a09068c2"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: beverloo X-GitHub-Recipient: httpwg-issues X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: http-issues@ietf.org Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.15 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jan 2016 12:33:05 -0000 ----==_mimepart_56aa0a7dcb1f0_46c83faa1b2012a09068c2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Each record currently includes between 1 and 256 octets of padding, while the default record size is set to 4096 octets. This is in many cases not sufficient, for example in the pad-to-next-power-of-two case. Extending the padding length to two octets will allow up to 65537 octets (65KB) of padding. I raised this on the ietf-http-wg list here: https://lists.w3.org/Archives/Public/ietf-http-wg/2016JanMar/0171.html Martin [raises a good point](https://lists.w3.org/Archives/Public/ietf-http-wg/2016JanMar/0175.html) about an upgrade path for existing users. I'll reply on the mailing list to not split the discussion. --- Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/issues/135 ----==_mimepart_56aa0a7dcb1f0_46c83faa1b2012a09068c2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

Each record currently includes between 1 and 256 octets of padding, while the default record size is set to 4096 octets. This is in many cases not sufficient, for example in the pad-to-next-power-of-two case.

Extending the padding length to two octets will allow up to 65537 octets (65KB) of padding.

I raised this on the ietf-http-wg list here:
https://lists.w3.org/Archives/Public/ietf-http-wg/2016JanMar/0171.html

Martin raises a good point about an upgrade path for existing users. I'll reply on the mailing list to not split the discussion.


Reply to this email directly or view it on GitHub.

----==_mimepart_56aa0a7dcb1f0_46c83faa1b2012a09068c2-- From nobody Thu Jan 28 04:34:00 2016 X-Original-To: http-issues@ietfa.amsl.com Delivered-To: http-issues@ietfa.amsl.com X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.454 X-Spam-Level: X-Spam-Status: No, score=-5.454 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham Date: Thu, 28 Jan 2016 04:33:56 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1453984436; bh=iIBRSPEW5HsBNLWX7HO5xGAZ+ywVwvw6hCKQQ0BDkhY=; h=From:Reply-To:To:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=f49vQOj35qS0LskxcPN2/5QW2+6IxzgiatgqcIQGRJJQ07sXgSoqR8X7pSFfY3BO6 PK3wAIhoc5dPtWyMcsMSaTZOQizgSLgF6hvhUu4hqnx+i7neZP/EOw7ezAhItotgO7 O2r093TDQNNJu+0ZwI9md7CqpEV0TbmexQH7q6E8= To: httpwg/http-extensions Subject: [http-extensions] Use two octets to indicate record padding length in httpbis-encryption-encoding (#136) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_56aa0ab4d2c89_3753fa3b7a5f2b811467b2"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: beverloo X-GitHub-Recipient: httpwg-issues X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: http-issues@ietf.org Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.15 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jan 2016 12:34:00 -0000 ----==_mimepart_56aa0ab4d2c89_3753fa3b7a5f2b811467b2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit This is a proposal to address issue #135 /cc @martinthomson You can view, comment on, or merge this pull request online at: https://github.com/httpwg/http-extensions/pull/136 -- Commit Summary -- * Use two octets to indicate record padding length in httpbis-encryption-encoding -- File Changes -- M draft-ietf-httpbis-encryption-encoding.md (10) -- Patch Links -- https://github.com/httpwg/http-extensions/pull/136.patch https://github.com/httpwg/http-extensions/pull/136.diff --- Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/136 ----==_mimepart_56aa0ab4d2c89_3753fa3b7a5f2b811467b2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

This is a proposal to address issue #135

/cc @martinthomson


You can view, comment on, or merge this pull request online at:

  https://github.com/httpwg/http-extensions/pull/136

Commit Summary

  • Use two octets to indicate record padding length in httpbis-encryption-encoding

File Changes

Patch Links:


Reply to this email directly or view it on GitHub.

----==_mimepart_56aa0ab4d2c89_3753fa3b7a5f2b811467b2-- From nobody Thu Jan 28 07:05:59 2016 X-Original-To: http-issues@ietfa.amsl.com Delivered-To: http-issues@ietfa.amsl.com X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.596 X-Spam-Level: X-Spam-Status: No, score=-5.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham Date: Thu, 28 Jan 2016 07:05:41 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1453993541; bh=dS8CDwFsss1wS5eF+H4CR3SBvxWBZJ3EXpJ6ZWrYC9o=; h=From:Reply-To:To:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=XzRRGUgQC7vIS2Hd4YMsLckilsXkHg0VZXXOYsPqVTdvUeUcCZeBXW1FUqk3w+Kkp HTsFmRKADl8UQhA2W82pq+8IJcpS+grCtzXG3kwLr6taFu/AzXorP15S+S3FgFcraD 3A1VDv0xWsfRWcbK+wKRkUDdAaPZQ0Xj/TZ+0/Wo= To: httpwg/http-extensions Subject: [http-extensions] Rename aesgcm128 to aesgcm to provide an update path (#137) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_56aa2e456840f_4cac3faa1b2012a05751d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: beverloo X-GitHub-Recipient: httpwg-issues X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: http-issues@ietf.org Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.15 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jan 2016 15:05:57 -0000 ----==_mimepart_56aa2e456840f_4cac3faa1b2012a05751d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit In order to allow existing applications to update from one octet of padding per record to two (PR #136, Issue #135), this PR renames "aesgcm128" to "aesgcm" as the value for the Content-Encoding header, as well as the parameter name in the Crypto-Key header. This also affects the context used for deriving the nonce and the content encryption key. Examples have been updated. What I did not update is the JWE mapping (currently "A128GCM"). Do we wish to change that to "AGCM", which may be less descriptive? You can view, comment on, or merge this pull request online at: https://github.com/httpwg/http-extensions/pull/137 -- Commit Summary -- * Rename aesgcm128 to aesgcm to provide an update path -- File Changes -- M draft-ietf-httpbis-encryption-encoding.md (62) -- Patch Links -- https://github.com/httpwg/http-extensions/pull/137.patch https://github.com/httpwg/http-extensions/pull/137.diff --- Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/pull/137 ----==_mimepart_56aa2e456840f_4cac3faa1b2012a05751d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

In order to allow existing applications to update from one octet of
padding per record to two (PR #136, Issue #135), this PR renames
"aesgcm128" to "aesgcm" as the value for the Content-Encoding header,
as well as the parameter name in the Crypto-Key header.

This also affects the context used for deriving the nonce and the
content encryption key. Examples have been updated.

What I did not update is the JWE mapping (currently "A128GCM"). Do
we wish to change that to "AGCM", which may be less descriptive?


You can view, comment on, or merge this pull request online at:

  https://github.com/httpwg/http-extensions/pull/137

Commit Summary

  • Rename aesgcm128 to aesgcm to provide an update path

File Changes

Patch Links:


Reply to this email directly or view it on GitHub.

----==_mimepart_56aa2e456840f_4cac3faa1b2012a05751d-- From nobody Thu Jan 28 16:25:23 2016 X-Original-To: http-issues@ietfa.amsl.com Delivered-To: http-issues@ietfa.amsl.com X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.399 X-Spam-Level: X-Spam-Status: No, score=-6.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_45=0.6, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham Date: Thu, 28 Jan 2016 16:25:17 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1454027117; bh=1374USECxhpw7/h6271XWx0uM/ZAF/YbPcUHHNvGHMU=; h=From:Reply-To:To:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=xtjNl0/078oHWLwPK4xR2IhrLgTMxRFP9B+DxPjZ3D4c4DVZilp5fynVohVBvLN7F a3ko+GsBzI7osU2qlzQEy3I/15zJZu01ZVDLYIMbthAhl7m4AmkXhSbi9PFUEwQAeL +vQarvXIN4BvwKnJmCCt5fqhPB3dRzrC7aTX5aAA= To: httpwg/http-extensions Subject: [http-extensions] Documenting Refresh: HTTP header (#138) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_56aab16d5f5a3_63f03faa1b2012a06149"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: karlcow X-GitHub-Recipient: httpwg-issues X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: http-issues@ietf.org Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.15 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2016 00:25:22 -0000 ----==_mimepart_56aab16d5f5a3_63f03faa1b2012a06149 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Maybe @reschke = In [RFC7538](http://tools.ietf.org/html/rfc7538#section-4) there is a men= tion of `meta refresh` in HTML. I have seen instances online of a `Refres= h` HTTP header. I haven't found any documentation about it in the past (o= r maybe I missed the appropriate RFC). I [met the header again yesterday]= (https://bugzilla.mozilla.org/show_bug.cgi?id=3D668275#c52) in an instanc= e of gmail Web site. When requesting `=E2=86=92 http --print hH https://mail.google.com/ 'User-Agent:Mozilla/5= .0 (Android 4.4.4; Mobile; rv:44.0) Gecko/44.0 Firefox/44.0' 'Accept-Lang= uage:en-US,en;q=3D0.5'` ```http HTTP/1.1 200 OK Alt-Svc: quic=3D":443"; ma=3D604800; v=3D"30,29,28,27,26,25" Alternate-Protocol: 443:quic,p=3D1 Cache-Control: private, max-age=3D604800 Content-Length: 306 Content-Type: application/xhtml+xml; charset=3DISO-8859-1 Date: Thu, 28 Jan 2016 00:57:39 GMT Expires: Thu, 28 Jan 2016 00:57:39 GMT Refresh: 0;URL=3Dhttps://mail.google.com/mail/ Server: GSE X-Content-Type-Options: nosniff X-Frame-Options: SAMEORIGIN X-XSS-Protection: 1; mode=3Dblock ``` You might not be able to reproduce gmail has tons of versions depending o= n the location, devices, headers, etc. I have started to [test a bit and write about it last year](http://www.ot= sukare.info/2015/03/26/refresh-http-header). It seems implemented uniform= ly, but that would require a bit more test. = What would be the best course of actions for documenting it? Maybe I can = give it a shot. = --- Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/issues/138= ----==_mimepart_56aab16d5f5a3_63f03faa1b2012a06149 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Maybe @r= eschke

In RFC7538 there is a mention of meta refresh in HTML. I have seen in= stances online of a Refresh HTTP header. I haven't found any= documentation about it in the past (or maybe I missed the appropriate RF= C). I met the header again yesterday in an instance of gmail Web site.

When requesting
=E2=86=92 http --print hH https://mail.google.com/ 'User-Agent:Mozi= lla/5.0 (Android 4.4.4; Mobile; rv:44.0) Gecko/44.0 Firefox/44.0' 'Accept= -Language:en-US,en;q=3D0.5'

HTTP/1.1 200 OK
Alt-Svc: quic=3D":443"; =
ma=3D604800; v=3D"30,29,28,27,26,25"
Alternate-Protocol: 443:=
quic,p=3D1
Cache-Control: private, =
max-age=3D604800
Content-Length: 306
Content-Type: applicatio=
n/xhtml+xml; charset=3DISO-8859-1
Date: Thu, 28 Jan 2016 0=
0:57:39 GMT
Expires: Thu, 28 Jan 201=
6 00:57:39 GMT
Refresh: 0;URL=3Dhttps:/=
/mail.google.com/mail/
Server: GSE
X-Content-Type-Options: =
nosniff
X-Frame-Options: SAMEORI=
GIN
X-XSS-Protection: 1; mod=
e=3Dblock

You might not be able to reproduce gmail has tons of versions dependin= g on the location, devices, headers, etc.

I have started to test a bit and write about it last year. It seems imp= lemented uniformly, but that would require a bit more test.

What would be the best course of actions for documenting it? Maybe I c= an give it a shot.

&m= dash;
Reply to this email directly or view it on GitHub.3D""

----==_mimepart_56aab16d5f5a3_63f03faa1b2012a06149-- From nobody Thu Jan 28 19:17:41 2016 X-Original-To: http-issues@ietfa.amsl.com Delivered-To: http-issues@ietfa.amsl.com X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.941 X-Spam-Level: X-Spam-Status: No, score=-4.941 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_12=2.059, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham Date: Thu, 28 Jan 2016 19:17:36 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1454037456; bh=If4BFgZveKQFY9Z4CFHn7UnKZjr6XE7tWsIT+g2wUak=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=SllqBfDYzqE6I2c8gRKAjIA+cDYfQrWKxtmc0JHb9EiSXXuRO8YOfdadSe4N7fMtv csv7TDS67lmuLzsGY7Q6+DktMiTiGSyHEqN8WOx3fBihySw+NrQbv+PxL2gQp0mEiE wB5hwB/nRhWnPAN4TEnnjdq+J7k6fsMDDBbbfPAk= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [http-extensions] Documenting Refresh: HTTP header (#138) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_56aad9d0b46cd_60b23fd1fab2b2c069687c2"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mnot X-GitHub-Recipient: httpwg-issues X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: http-issues@ietf.org Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.15 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2016 03:17:39 -0000 ----==_mimepart_56aad9d0b46cd_60b23fd1fab2b2c069687c2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit A short Internet-Draft might do it. Would need to align with https://html.spec.whatwg.org/#attr-meta-http-equiv-refresh @annevk thoughts? --- Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/issues/138#issuecomment-176549826 ----==_mimepart_56aad9d0b46cd_60b23fd1fab2b2c069687c2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

A short Internet-Draft might do it. Would need to align with https://html.spec.whatwg.org/#attr-meta-http-equiv-refresh

@annevk thoughts?


Reply to this email directly or view it on GitHub.

----==_mimepart_56aad9d0b46cd_60b23fd1fab2b2c069687c2-- From nobody Fri Jan 29 06:17:25 2016 X-Original-To: http-issues@ietfa.amsl.com Delivered-To: http-issues@ietfa.amsl.com X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.941 X-Spam-Level: X-Spam-Status: No, score=-4.941 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_12=2.059, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham Date: Fri, 29 Jan 2016 06:17:21 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1454077041; bh=vp4hVKMZJiFT51fxBod1s21PxdK/9Mw4N35OCK4rzag=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KhjfkKfwn5Z7sip1gx9M6tTkF/6PYKaHlT8cfaoKld4os3S8e+1dwusujYloEI7Oz GPjAumeui9uMmDOseW4p4zY/atQdDoUWOSATsuvmUsogZNG1XI96CikTHNC4agQjzx NVguqEkBmI7FvMD1lhA3u7ujahlLLOzFtuNff8BI= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [http-extensions] Documenting Refresh: HTTP header (#138) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_56ab7471dd458_5ef73f8de20592b8294384"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: annevk X-GitHub-Recipient: httpwg-issues X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: http-issues@ietf.org Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.15 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2016 14:17:24 -0000 ----==_mimepart_56ab7471dd458_5ef73f8de20592b8294384 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I don't see how that would imply that, but I also have not heard about non-browser support. --- Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/issues/138#issuecomment-176777048 ----==_mimepart_56ab7471dd458_5ef73f8de20592b8294384 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I don't see how that would imply that, but I also have not heard about non-browser support.


Reply to this email directly or view it on GitHub.

----==_mimepart_56ab7471dd458_5ef73f8de20592b8294384-- From nobody Fri Jan 29 20:51:22 2016 X-Original-To: http-issues@ietfa.amsl.com Delivered-To: http-issues@ietfa.amsl.com X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.941 X-Spam-Level: X-Spam-Status: No, score=-4.941 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_12=2.059, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham Date: Fri, 29 Jan 2016 20:51:17 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1454129477; bh=91FPOXlI+33cdDG7Xqt6p27CG2uy8JUcCUMopHONtAw=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=tzndbdFw5yuKbF2PkRFkyCmF7Isljg8moMy+hLmKtxiYPmFjdaxgYwB8hM+3wf9mn FJ70LxH1STEG6qfy49k46wxYogqR2rKpCOiCrRVefz2fYajXjWhuiKQvpvf0axk+nC aOnCmdfEqNdzwjHrcgOoyXIPuxibCg0tpk3WhZQQ= To: httpwg/http-extensions In-Reply-To: References: Subject: Re: [http-extensions] Documenting Refresh: HTTP header (#138) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_56ac4145db609_242d3fc4e21c32c0152563a"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: mnot X-GitHub-Recipient: httpwg-issues X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: http-issues@ietf.org Archived-At: Message-ID: From: HTTP issue updates X-BeenThere: http-issues@ietf.org X-Mailman-Version: 2.1.15 Reply-To: http-issues@ietf.org List-Id: HTTP issue updates List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jan 2016 04:51:22 -0000 ----==_mimepart_56ac4145db609_242d3fc4e21c32c0152563a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I don't think it particularly matters where it's defined, as long as we make sure it's reviewed by the appropriate folks and registered. --- Reply to this email directly or view it on GitHub: https://github.com/httpwg/http-extensions/issues/138#issuecomment-177067174 ----==_mimepart_56ac4145db609_242d3fc4e21c32c0152563a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

I don't think it particularly matters where it's defined, as long as we make sure it's reviewed by the appropriate folks and registered.


Reply to this email directly or view it on GitHub.

----==_mimepart_56ac4145db609_242d3fc4e21c32c0152563a--