Chromium Quic client-server interaction.

[Dennis Cattoni]

Hi everyone! I correctly followed the instructions provided by the guide https://www.chromium.org/quic/playing-with-quic/.

I can correctly run the toy server and client with the following commands:

./out/Default/quic_server \
  --quic_response_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

./out/Default/quic_client --host=127.0.0.1 --port=6121 --allow_unknown_root_cert https://www.example.org/

______________________________________________________________________

I have to make some protocol testing with specific file sizes, I tryed to make dummy .txt files in the path "/tmp/quic-data/www.example.org" with a specific size of 10Kb but the server doesn't run, giving the following error:

./out/Default/quic_server   --quic_response_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
[1110/143246.580749:FATAL:quic_memory_cache_backend.cc(73)] Headers invalid or empty, ignoring: /tmp/quic-data/www.example.org/10KB_file.txt
#0 0x7ffb654c1f0c base::debug::CollectStackTrace()
#1 0x7ffb6547268a base::debug::StackTrace::StackTrace()
#2 0x7ffb65472645 base::debug::StackTrace::StackTrace()
#3 0x7ffb65196309 logging::LogMessage::~LogMessage()
#4 0x558b98319492 quic::QuicMemoryCacheBackend::ResourceFile::Read()
#5 0x558b9831beb6 quic::QuicMemoryCacheBackend::InitializeBackend()
#6 0x558b982d1677 quic::QuicToyServer::MemoryCacheBackendFactory::CreateBackend()
#7 0x558b982c2489 net::QuicSimpleServerBackendFactory::CreateBackend()
#8 0x558b982d2046 quic::QuicToyServer::Start()
#9 0x558b982c26ff main
#10 0x7ffb63923083 __libc_start_main
#11 0x558b982c239a _start

Trace/breakpoint trap (core dumped)

______________________________________________________________________

Did someone encountered the same issue and eventually have fixed it? 

I read also this topic and it suggests that any element in the index.html must have the attribute "X-original-Url":
https://groups.google.com/a/chromium.org/g/proto-quic/c/VytEB9rM8_A/m/4xVy4tLIpacJ

[Adam Rice]

It looks like it expects the file to be structured something like:

HTTP/1.1 200 OK

Content-Type: text/plain

Actual file contents start here.

--
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 view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/proto-quic/dab7612f-c988-43d0-95ca-62ff65a323f1n%40chromium.org.

[mhtv24. com]

সোম, ১৩ নভেম্বর, ২০২৩ ২:০২ PM তারিখে Adam Rice <ri...@chromium.org> লিখেছেন:

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/proto-quic/CAC_ixdyooyTFL%3D_cVLFC_TqKiC2w_UPJrmh9ptpgp5HeH4AjTw%40mail.gmail.com.

[Dennis Cattoni]

Thank you so much Adam! It worked and I run the server correctly! Thank you much.
But for requesting the 10KB_file.txt file (on the client side) what's the correct command? Looks like I'm having issues also in requesting my testing file on the client's side.

$ ./out/Default/quic_client --host=127.0.0.1 --port=6121 --allow_unknown_root_cert /tmp/quic-data/www.example.org/10KB_file.txt

gives me:

[1113/132402.857870:ERROR:cert_verify_proc_builtin.cc(621)] No net_fetcher for performing AIA chasing.
[1113/132402.862512:WARNING:proof_verifier_chromium.cc(449)] Failed to verify certificate chain: net::ERR_CERT_COMMON_NAME_INVALID
6373734140544:error:1000007d:SSL routines:OPENSSL_internal:CERTIFICATE_VERIFY_FAILED:../../third_party/boringssl/src/ssl/handshake.cc:393:
[1113/132402.862611:ERROR:tls_handshaker.cc(161)] TLS handshake failure (ENCRYPTION_HANDSHAKE) 46: certificate unknown
Failed to connect to 127.0.0.1:6121. QUIC_TLS_CERTIFICATE_UNKNOWN TLS handshake failure (ENCRYPTION_HANDSHAKE) 46: certificate unknown