Re: WSGI 2.0 Round 2: requirements and call for interest

--===============5261181268846582838==
Content-Type: multipart/signed; boundary="Apple-Mail=_ABCB5EFE-789A-479E-AC77-B2C8298C0B41"; protocol="application/pgp-signature"; micalg=pgp-sha256


--Apple-Mail=_ABCB5EFE-789A-479E-AC77-B2C8298C0B41
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On 6 Jan 2016, at 09:19, Aymeric Augustin =
<aymeric.augustin-o/5/jSaJEHk+NdeTPqioyti2O/[email protected]> wrote:
>=20
> Hello Beno=C3=AEt,
>=20
> Thanks for clarifying that you also had the reverse problem in mind, =
headers sent by applications. This side is less problematic in the sense =
that application authors can adapt to stronger requirements.
>=20
> In general this is a bit of a mess due to differences between what the =
RFC 2616 says and what browsers do in practice. That=E2=80=99s why I =
believe the pragmatic solution is to exchange bytes. (This isn=E2=80=99t =
a major issue in the grand scheme of things anyway.)
>=20
> Best regards,
>=20

Folks, just a reminder: RFC 2616 is dead. RFC 7230 says that *newly =
defined* header fields should limit their field values to US-ASCII, but =
older header fields are a crapshoot (though it notes that =E2=80=9Cin =
practice, most=E2=80=9D header field values use US-ASCII).

Regardless, it seems to me that the correct method of communicating =
field values would have been byte strings.

Cory


--Apple-Mail=_ABCB5EFE-789A-479E-AC77-B2C8298C0B41
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJWjPjlAAoJEHD+F/imQ+FbU20QANLNA/XgWsgkPsQqafLm21wq
TCxemsVsz7L9w1IwO6yFtcP6C309+SWs/a+70uNhtHcosE2UQEhvouqN5cJsE+8u
sfcNVsXk6HoMmRMga8xCmyjcdmU9eAqoiZNt0r6CrSTDGCr/XkmNfp4B4Jo1FNtH
LChOpsJIlR5o02yBhgowGdswZMi50Sz9ZMbIGIEgBeCfefI5H82fBE80bFRAQM6x
S2fk5cQvkcU221zB0WlkxuzCbAjzyfOlXJ08lQrYy9tJy3F4O/+4no2gXxKArIrg
KIHPsGp9r9q+eH5zX4sGXm+A5pY6rfJkCOF3paL6KI2VyRSuo1OUupasbEYTUMw6
9DHNygwMsCDbfY8Vn8+zOtZbtkJM9MQuPQ5NsZJP1yDxTJM4f96Up25iEU0mEK0H
Gfc7/eBB/Ixs67BhXTbq1leN5ILRGzVRz+TI9duDSrqM4s9SZWWIfi1AbTiQwskA
2018le3sUoEp7Om5YfSLS+RFQ2itgyEP4IA1HZ+ELvxIoszqn3NTdcOZN9RU/A59
5ePy7KnjEWqDmE7ikhz3ZbkmqZM0EOkbeqFilBeFCqyYOCoupr/Neww34INrP+ZF
S4ENmpfcTWnAe7WcsO4dsM4zaKNw4OmAl7uFSifHEb38TOjVi/sVjD3fD7YMO898
CGCfHUvzpwgStnRP6ppB
=jA5L
-----END PGP SIGNATURE-----

--Apple-Mail=_ABCB5EFE-789A-479E-AC77-B2C8298C0B41--

--===============5261181268846582838==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Web-SIG mailing list
[email protected]
Web SIG: http://www.python.org/sigs/web-sig
Unsubscribe: https://mail.python.org/mailman/options/web-sig/gcpw-web-sig%40m.gmane.org

--===============5261181268846582838==--