NGINX HPACK decode failure

[Jesse Wilson]

I’m attempting to diagnose a bug report
<https://github.com/square/okhttp/issues/1897> against OkHttp, the HTTP/2
client for Android that I help to maintain.


Some of my users have run into problems making HTTP/2 requests against
NGINX. I believe the problem is that NGINX’s HPACK decoder can’t decode the
following:

020347455404232f726573742f76312f73697465732f37333335303032312f70
6f7374732f363039313501187075626c69632d6170692e776f72647072657373
2e636f6d060568747470730f00057574662d380f2b0c6f6b687474702f322e35
2e30

It fails, and reports a PROTOCOL_ERROR to the client. Instead, it should
have decoded to this:

:method: GET
:path: /rest/v1/sites/73350021/posts/60915
:authority: public-api.wordpress.com
:scheme: https
accept-charset: utf-8
user-agent: okhttp/2.5.0

Please confirm. Unfortunately, I can’t tell you the particulars of the
version of NGINX deployed on wordpress.com that triggers this.

Thanks!
– Jesse
​
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20151018/4fc18c6a/attachment.html>