QUIC Test server + Chrome

[Eduardo Castellanos]

Hello, 

I had managed to get Chrome to request websites from the QUIC test server without any issues like a week ago. Now I came back to continue my work and I keep getting "80:Broken p=1.000000" in the "chrome://net-internals/#spdy" tab on the Alternate protocol mappings table. 

I haven't changed much my setup, but I'm stumped as of why QUIC is not working anymore. I have done a "git rebase-update", gsync, and recompiled everything with ninja, but I'm still unable to get Chrome to work with the toy server. The output for the toy server is here: http://pastebin.com/XMKrdvF6 . Can anyone please help me out?

Thanks!

E.Castellanos

[Ryan Hamilton]

Looks like the problem is this:

[1117/155348:VERBOSE1:quic_protocol.cc(184)] Unsupported QuicTag version: Q021

Which version of Chrome are you using to speak to the toy server? You'll need to use a version of Chrome that supports the same QUIC version as the toy server (perhaps Dev or Canary channel)

Cheers,

Ryan

--
You received this message because you are subscribed to the Google Groups "QUIC Prototype Protocol Discussion group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to proto-quic+...@chromium.org.
To post to this group, send email to proto...@chromium.org.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.

[Eduardo Castellanos]

Thank you, that was actually the problem. I tested with Canary and it worked perfectly. I guess I had just been lucky with Chrome before. 

Regards

[Eduardo Castellanos]

Ok, so I'm trying to clone a Wikipedia page to test, and I'm having a problem with overly long URLs (more than 593 characters). For example this URL: "http://bits.wikimedia.org/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"

will trigger this on the quic_server:

[1118/150009:VERBOSE1:spdy_framer.cc(2291)] Unable to read header value (11 of 11).

[1118/150009:VERBOSE1:spdy_framer.cc(2299)] Duplicate header ':host' (1 of 11).

So I looked into it and tracked it down to the fact that after the first failed attempt to read all the headers the headers_ buffer in quic_spdy_server_stream.cc is not cleared, so on the second attempt it will fail because it already has the header. 

[李辉]

How to build local server to test the QUIC,Is there any software like Apache?I am interested in it and want know more details about your test.

在 2014年11月19日星期三UTC+8上午8时34分49秒，Eduardo Castellanos写道：

[Ryan Hamilton]

Doh! If you clear headers_ in QuicSpdyServerStream::ParseRequestHeaders just after if (len == 0) does that solve the problem? If so, I'll land a fix. 

--

[Eduardo Castellanos]

That's exactly what I did. :) It was way too late for me to finish the email properly. 

Cheers,

Sent from my mobile device. Please excuse brevity or typos.

[Prasenjeet Biswal]

Hello Eduardo,

I am trying to request the cached sites using chrome from the quic toy server.Currently I am able to connect to the toy server but getting a "bad" response from it.

Can you guide me how to use chrome to request pages from quic server?

Thanks
Prasenjeet Biswal