mirror/openssl
2
0
Fork 0
mirror of https://github.com/openssl/openssl.git synced 2024-11-27 05:21:51 +08:00
Code Issues Packages Projects Releases Wiki Activity
bce3a8d57e
openssl/demos/http3
History
Neil Horman 2000281dad Convert demos to primary build system 
Reviewed-by: Nicola Tuveri <nic.tuv@gmail.com>
Reviewed-by: Tim Hudson <tjh@openssl.org>
Reviewed-by: Paul Dale <ppzgs1@gmail.com>
Reviewed-by: Tom Cosgrove <tom.cosgrove@arm.com>
(Merged from https://github.com/openssl/openssl/pull/24047)
2024-04-12 08:02:19 -04:00
..
build.info Convert demos to primary build system 2024-04-12 08:02:19 -04:00
gen_nghttp3.pl Convert demos to primary build system 2024-04-12 08:02:19 -04:00
Makefile demos/http3: Use SSL_write_ex2() together with SSL_WRITE_FLAG_CONCLUDE 2024-03-01 10:56:16 +01:00
ossl-nghttp3-demo.c Convert demos to primary build system 2024-04-12 08:02:19 -04:00
ossl-nghttp3.c Copyright year updates 2024-04-09 13:43:26 +02:00
ossl-nghttp3.h Rename 2023-10-19 08:28:59 +01:00
README.md quic http3 demo: minor updates 2023-11-08 11:12:55 +11:00

README.md

HTTP/3 Demo using OpenSSL QUIC and nghttp3

This is a simple demo of how to use HTTP/3 with OpenSSL QUIC using the HTTP/3 library “nghttp3”.

The demo is structured into two parts:

  • an adaptation layer which binds nghttp3 to OpenSSL's QUIC implementation (ossl-nghttp3.c);
  • a simple application which makes an HTTP/3 request using this adaptation layer (ossl-nghttp3-demo.c).

The Makefile in this directory can be used to build the demo on *nix-style systems. You will need the nghttp3 library and header file. On Ubuntu, these can be obtained by installing the package libnghttp3-dev.

Running the Demo

Depending on your system configuration it may be necessary to set the SSL_CERT_FILE or SSL_CERT_DIR environment variables to a location where trusted root CA certificates can be found.

After building by running make, run ./ossl-nghttp3-demo with a hostname and port as the sole argument:

$ make
$ LD_LIBRARY_PATH=../.. ./ossl-nghttp3-demo www.google.com:443

The demo produces the HTTP response headers in textual form as output followed by the response body.

See Also