devsisters / goquic

QUIC support for Go
http://devsisters.github.io/goquic/
BSD 3-Clause "New" or "Revised" License
944 stars 100 forks source link

QUIC indicator not showing up #41

Open anirudt opened 8 years ago

anirudt commented 8 years ago

Hi,

I wanted to set up a working QUIC server and client system working. I have used this repository's server as my QUIC server, bootstrapping it over a SimpleHTTPServer in Python. As far as the client is concerned, I am using Chrome, having enabled its QUIC setting. However, when I run the server, the log still says H2, or HTTP 2.0. Thus, I have a few questions:

  1. Is there any extra setting from the server or the client side that is required to use the devsister's QUIC server with either of the QUIC enabled client browsers [i.e. Chrome/Opera]?
  2. Is there some other packet that we need to look out for?

I must thank you for your repository, and your blog. It was quite insightful! Hoping to obtain some fruitful discussions from the above questions.

Thanking you, With Best Regards anirudt

hodduc commented 8 years ago

Hi!

anirudt commented 8 years ago

Hi,

Which version of Chrome are you using? Old chrome (<= 51.x) needs some extra configuration (whitelisting).

I am using Chrome version 53.0.2785.89. I have enabled the flags at chrome://flags/

QUIC uses UDP packet as base layer. If your network blocks or whitelists UDP packets, QUIC will not work.

My network allows UDP as well.

Are you using valid SSL certificate? If this is the case, you may build server with debug mode then check server log with verbose logging turned on.

Yes, I am using a valid SSL certificate. The page seems to be loading, but Wireshark still only reports it as TCP.