New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 616972 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

quic_server quic_client reports error SERVER_CONFIG_INCHOATE_HELLO_FAILURE during connect

Reported by keniee...@gmail.com, Jun 3 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

Example URL:
https://www.chromium.org/quic/playing-with-quic

Steps to reproduce the problem:
1. download the quic source code on ubuntu
2. follow the instruction in https://www.chromium.org/quic/playing-with-quic

3. then run quic server. run quic client.
it connects fail 

What is the expected behavior?
quic client shall connect with quic server ok.

What went wrong?
quick client can't connect quic server

error message is: quick server rej   RREJ: SERVER_CONFIG_INCHOATE_HELLO_FAILURE

Did this work before? N/A 

Chrome version: 50.0.2661.102  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 21.0 r0

I debug the source code, it turns out 

void QuicCryptoServerConfig::ValidateClientHello(

 client_hello.GetStringPiece(kSCID, &requested_scid);

}
the request_scid returns just empty string. 

so, the server can't find the right config .
 
Cc: jri@chromium.org rch@chromium.org
Components: -Internals>Network Internals>Network>QUIC

Comment 2 by rch@chromium.org, Jun 13 2016

Labels: Needs-Feedback
SERVER_CONFIG_INCHOATE_HELLO_FAILURE is expected the first time a client connects to a server. I suspect this is not the root cause of your problem. Can you attach the full output from your server and your client?
kenieevan@, can you send the full output as rch@ requested?

Comment 4 by mge...@chromium.org, Jul 19 2016

Status: Archived (was: Unconfirmed)
Closing this, since we don't have enough information to figure out what's wrong. If you're still seeing the problem, please open a new bug with the information rch requested.

Comment 5 by keniee...@gmail.com, Jul 19 2016

hello, rch

sorry for missing the mail.. I am just busy at some other projects.

I solve this problem by 

add the option when running quic_client --disable-certificate-verification 

if i don't add this option, the ssl verify fail, and the connection will be closed .However, I do follow the document to set the certificate right.



thanks.


Sign in to add a comment