quic test,help

145 views
Skip to first unread message

Jian Zhu

unread,
Dec 16, 2015, 7:38:57 AM12/16/15
to Chromium-dev
Hi all:
I came across some problem when i test quic as below page:
http://www.chromium.org/quic/playing-with-quic

After i wget "https://www.example.org", i can't find the content asked to manually edited as below:
  • remove "Transfer-Encoding: chunked"
  • remove "Alternate-Protocol: ..."  (the example config calls for port 6121 below)
  • add X-Original-Url: https://www.example.org/

if i don't manually edith index.html, some failure happened when performing quic test. In the quic_client side, it outputs as below:

./out/Default/quic_client --host=127.0.0.1 --port=6121 https://www.example.org/
Connected to 127.0.0.1:6121
Request:
headers:
 :authority: www.example.org
 :method: GET
 :path: /
 :scheme: https
body:

Response:
headers: HTTP/1.1 500 OK
status: 500
content-length: 3

body: bad
Request failed (500).


In the quic_server side, it outputs as below:
./out/Default/quic_server --quic_in_memory_cache_dir=/
tmp/quic-data/www.example.org --certificate_file=net/tools/quic/certs/out/leaf_cert.pem  --key_file=net/tools/quic/certs/out/leaf_cert.pkcs8
[1216/052728:WARNING:quic_framer.cc(593)] Unable to process packet header.  Stopping parsing.

Can someone kindly give some help on the above failure of quic test ?

What's more, can anyone kindly tell me how to test using quic client and server to transmit data file and test the transmitting speed?

Jian Zhu

unread,
Dec 16, 2015, 11:02:32 PM12/16/15
to Chromium-dev
I find I miss one step:
"In addition to the server's certificate and public key, this script will also generate a CA certificate (net/tools/quic/certs/out/2048-sha256-root.pem) which you will need to add to your OS's root certificate store in order for it to be trusted during certificate validate. For doing this on linux, please see these instructions."

I think maybe this missing step may be the reason for the failure of my quic test. However when i try to perform this step as below command:
"certutil -d sql:$HOME/.pki/nssdb -A -t "C,," -n "QUIC Server Root CA"  -i "2048-sha256-root.pem"
The output info is:
"certutil: function failed: SEC_ERROR_BAD_DATABASE: security library: bad database"

Can anyone kindly help me, tell me whether the missing step is the reason for failure of quic test, if yes, please tell me how to fix it, if not, please kindly me how to do the quic test successfully?
Any comment or suggestion is warmly appreciated.

certutil -d sql:$HOME/.pki/nssdb -A -t "C,," -n "QUIC Server Root CA"  -i "2048-sha256-root.pem"
certutil: function failed: SEC_ERROR_BAD_DATABASE: security library: bad database.

Jian Zhu

unread,
Dec 16, 2015, 11:04:48 PM12/16/15
to Chromium-dev
My os is ubuntu 12.04 LTS(gcc 4.8.1) and the chromium is built successfully.

Jian Wen

unread,
Dec 19, 2015, 10:19:03 AM12/19/15
to Chromium-dev
Hello,

Did you add the X-Original-Url header?

My OS is Ubuntu 14.04.3 LTS.
The following command works for me .
certutil -d sql:$HOME/.pki/nssdb -A -t "C,," -n "www.example.org" -i net/tools/quic/certs/out/2048-sha256-root.pem
Reply all
Reply to author
Forward
0 new messages