Steps to reproduce the problem:
1. set up mitm proxy 
2. set up proxy on android phone
3. install the certificate following https://mitmproxy.org/doc/certinstall.html#docCA
4. Connect to a server supporting both http2 and quic e.g., https://app.snapchat.com/discover/channel_list?region=US

What is the expected behavior?
We should not be able to eavesdrop the traffic using man in the middle proxy.

What went wrong?
We can see the actually traffic as below.
/Users/zhihua.wen/git/android/snapchat/app/build/intermediates/exploded-aar/com.brightcove.player/android-sdk/4.3.2/res/drawable-hdpi-v4/no_edge_attribute.png: libpng warning: iCCP: Not recognizing known sRGB profile that has been edited

/Users/zhihua.wen/git/android/snapchat/app/build/intermediates/exploded-aar/com.brightcove.player/android-sdk/4.3.2/res/drawable-hdpi-v4/raised_edges.png: libpng warning: iCCP: No2015-08-18 14:42:45 GET https://app.snapchat.com/discover/channel_list?region=US
                        ← 200 application/json 72.66kB 9.83MB/s
Request                                                                                   Response
X-Snapchat-Request-Id:  55d3a5ad00ff00ffc6afe50253b10001737e6665656c696e736f6e6963652d68726400016d617374657234373034300001020177
X-Snapchat-Notice:      Snapchat Private APIs - Unauthorized use is prohibited.
Pragma:                 Public
Content-Type:           application/json; charset=UTF-8
Date:                   Tue, 18 Aug 2015 21:37:49 GMT
Server:                 Google Frontend
Cache-Control:          public, max-age=300
Age:                    296
Alternate-Protocol:     443:quic,p=1
Alt-Svc:                quic=":443"; p="1"; ma=604800
Accept-Ranges:          none
Vary:                   Accept-Encoding
Transfer-Encoding:      chunked
...

Did this work before? No 

Chrome version: 44.0.2403.155  Channel: stable
OS Version: OS X 10.10.3
Flash Version: Shockwave Flash 18.0 r0