Chrome ver. 67 to switch from HTTPS to QUIC using alt-svc header

[N P]

Hello, 

I'm fairly new to QUIC. 

1. I have  the quic toy client & server running. I'm able to use QUIC to get files from the quic server. 
   
2. I'm also able to "force" the chrome browser to get files from the toy quic server using: 
3. ./out/Default/chrome  --disable-gpu --remote-debugging-port=9222   user-data-dir=/tmp/chrome-profile  --no-proxy-server --enable-quic --origin-to-force-quic-on=www.example.org:443 --host-resolver-rules='MAP www.example.org IP_OF_QUIC_SERVER:6121' https://www.example.org

I want to use HTTP headers to get chrome to switch between HTTPS & QUIC by itself, without forcing it. I used NGINX to handle the initial HTTPS requests & return a "200" with the following header config in the nginx.conf file: 

add_header Alt-Svc "quic=:6121; persist=1; v=44,39";

The first request to the domain is over HTTPS (to be expected), but I was expecting that every subsequent request to the domain would be over QUIC (because of the Alt-Svc header). But the browser doesn't make the switch. 

I've tried using the IETF standard: "hq" as the alt-svc header, but that didn't help. 

I can confirm that certs isn't an issue, since I'm able to get content when QUIC is "forced" using the command I mentioned in #3 above. 

Any ideas, what am I missing? 

Thank you, 

NP 

[ChengPing Cai]

I also  encountered the same problem as you, did you solve it? expect your reply.