litespeed-quic/README.md

155 lines
3.7 KiB
Markdown
Raw Normal View History

[![Build Status](https://travis-ci.org/litespeedtech/lsquic.svg?branch=master)](https://travis-ci.org/litespeedtech/lsquic)
[![Build Status](https://api.cirrus-ci.com/github/litespeedtech/lsquic.svg)](https://cirrus-ci.com/github/litespeedtech/lsquic)
[![Build status](https://ci.appveyor.com/api/projects/status/kei9649t9leoqicr?svg=true)](https://ci.appveyor.com/project/litespeedtech/lsquic)
2018-04-23 18:49:50 +00:00
LiteSpeed QUIC (LSQUIC) Library README
2017-09-22 21:00:03 +00:00
=============================================
Description
-----------
LiteSpeed QUIC (LSQUIC) Library is an open-source implementation of QUIC
functionality for servers and clients. It is released in the hope to speed
2017-09-22 21:00:03 +00:00
the adoption of QUIC. Most of the code in this distribution is used in
our own products: LiteSpeed Web Server, LiteSpeed ADC, and OpenLiteSpeed.
We think it is free of major problems. Nevertheless, do not hesitate to
report bugs back to us. Even better, send us fixes and improvements!
2017-09-22 21:00:03 +00:00
Currently supported QUIC versions are Q039, Q043, Q046, and ID-22. Support
for newer versions will be added soon after they are released.
2017-09-22 21:00:03 +00:00
Documentation
-------------
The documentation for this module is admittedly sparse. The API is
documented in include/lsquic.h. If you have doxygen, you can run
`doxygen dox.cfg` or `make docs`. The example program is
2017-09-22 21:00:03 +00:00
test/http_client.c: a bare-bones, but working, QUIC client. Have a look
in EXAMPLES.txt to see how it can be used.
Requirements
------------
2017-09-22 21:00:03 +00:00
To build LSQUIC, you need CMake, zlib, and BoringSSL. The example program
uses libevent to provide the event loop.
2017-09-22 21:00:03 +00:00
Building BoringSSL
------------------
BoringSSL is not packaged; you have to build it yourself. The process is
straightforward. You will need `go` installed.
1. Clone BoringSSL by issuing the following command:
```
git clone https://boringssl.googlesource.com/boringssl
cd boringssl
```
You may need to install pre-requisites like zlib and libevent.
2019-09-16 13:09:08 +00:00
2. Use specific BoringSSL version
```
git checkout 32e59d2d3264e4e104b355ef73663b8b79ac4093
```
3. Patch the library
This patch is required for IETF QUIC support.
```
patch -p1 -i ../patches/boringssl-meds.patch
```
4. Compile the library
```
cmake . && make
```
Remember where BoringSSL sources are:
```
BORINGSSL=$PWD
```
If you want to turn on optimizations, do
```
cmake -DCMAKE_BUILD_TYPE=Release . && make
```
Building LSQUIC Library
-----------------------
LSQUIC's `http_client`, `http_server`, and the tests link BoringSSL
libraries statically. Following previous section, you can build LSQUIC
as follows:
1. Get the source code
```
git clone https://github.com/litespeedtech/lsquic.git
cd lsquic
git submodule init
git submodule update
```
2. Compile the library
```
# $BORINGSSL is the top-level BoringSSL directory from the previous step
cmake -DBORINGSSL_DIR=$BORINGSSL .
make
```
3. Run tests
```
make test
```
Building with Docker
---------
2019-09-16 14:17:30 +00:00
The library and the example client and server can be built with Docker.
Initialize Git submodules:
```
cd lsquic
git submodule init
git submodule update
```
Build the Docker image:
```
docker build -t lsquic .
```
2019-09-16 14:17:30 +00:00
Then you can use the examples from the command line. For example:
```
2019-09-16 14:17:30 +00:00
sudo docker run -it --rm lsquic http_client -s www.google.com -p / -o version=Q046
sudo docker run -p 12345:12345/udp -v /path/to/certs:/mnt/certs -it --rm lsquic http_server -c www.example.com,/mnt/certs/chain,/mnt/certs/key
```
Platforms
---------
The library has been tested on the following platforms:
- Linux
2018-05-04 20:24:56 +00:00
- i386
- x86_64
- ARM (Raspberry Pi 3)
- FreeBSD
- i386
- MacOS
- x86_64
- Windows (this needs updating for the server part, now broken)
- x86_64
2017-09-22 21:00:03 +00:00
Have fun,
LiteSpeed QUIC Team.
Copyright (c) 2017 - 2019 LiteSpeed Technologies Inc