- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Wed, 14 Dec 2016 11:35:16 +0100
- To: Poul-Henning Kamp <phk@phk.freebsd.dk>, Alexey Melnikov <alexey.melnikov@isode.com>
- Cc: Matthew Kerwin <matthew@kerwin.net.au>, Kari Hurtta <hurtta-ietf@elmme-mailer.org>, Ilari Liusvaara <ilariliusvaara@welho.com>, HTTP working group mailing list <ietf-http-wg@w3.org>, Poul-Henning Kamp <phk@varnish-cache.org>
On 2016-12-14 11:23, Poul-Henning Kamp wrote: > -------- > In message <3a65ca44-f652-3b14-6d64-46f35b32df57@isode.com>, Alexey Melnikov wr > ites: > >> IETF has published BCP 137, which should be followed, unless there is a >> very good reason not to: >> https://www.rfc-editor.org/bcp/bcp137.txt >> >> See section 5.1. > > So many RFCs, so little time... > > EmbeddedUnicodeChar = %x5C.75.27 4*6HEXDIG %x27 > > That works for me, but HPACK is not a big fan of it: > > 19 + 6 + 11 + [4:6] * [5:6] + 11 = [67:83] > > Is that a show-stopper for anybody in Asia ? Why are we concerned with HPACK? Wouldn't we convert to raw UTF-8 before HPACKing? Best regards, Julian
Received on Wednesday, 14 December 2016 10:37:45 UTC