XQUIC Library released by Alibaba is …
… a client and server implementation of QUIC and HTTP/3 as specified by the IETF. Currently supported QUIC versions are v1 and draft-29.
… OS and platform agnostic. It currently supports Android, iOS, HarmonyOS, Linux, macOS and Windows(v1.2.0). Most of the code is used in our own products, and has been tested at scale on android, iOS apps, as well as servers.
… still in active development. Interoperability is regularly tested with other QUIC implementations.
- All big features conforming with RFC 9000, RFC9001, RFC9002, RFC9114 and RFC9204, including the interface between QUIC and TLS, 0-RTT connection establishment, HTTP/3 and QPACK.
- ALPN Extension conforming with RFC7301
- Pluggable congestion control: NewReno, Cubic, BBR and BBRv2, ...
- Pluggable cryptography, integration with BoringSSL and BabaSSL
- Cross-platform implementation, support Android, iOS, HarmonyOS, Linux, macOS and Windows(v1.2.0)
To build XQUIC, you need
- CMake
- BoringSSL or BabaSSL
To run test cases, you need
- libevent
- CUnit
XQUIC can be built with BabaSSL(Tongsuo) or BoringSSL.
sudo apt-get install -y build-essential libevent-dev
# get XQUIC source code
git clone https://github.com/alibaba/xquic.git; cd xquic
# get and build BoringSSL
git clone https://github.com/google/boringssl.git ./third_party/boringssl; cd ./third_party/boringssl
mkdir -p build && cd build
cmake -DBUILD_SHARED_LIBS=0 -DCMAKE_C_FLAGS="-fPIC" -DCMAKE_CXX_FLAGS="-fPIC" ..
make -j ssl crypto
cd ..
SSL_TYPE_STR="boringssl"
SSL_PATH_STR="${PWD}"
cd ../..
# build XQUIC with BoringSSL
# When build XQUIC with boringssl, by default XQUIC will use boringssl
# in third_party. If boringssl is deployed in other directories, SSL_PATH could be
# used to specify the search path of boringssl
git submodule update --init --recursive
mkdir -p build; cd build
cmake -DGCOV=on -DCMAKE_BUILD_TYPE=Debug -DXQC_ENABLE_TESTING=1 -DXQC_SUPPORT_SENDMMSG_BUILD=1 -DXQC_ENABLE_EVENT_LOG=1 -DXQC_ENABLE_BBR2=1 -DXQC_ENABLE_RENO=1 -DSSL_TYPE=${SSL_TYPE_STR} -DSSL_PATH=${SSL_PATH_STR} ..
# exit if cmake error
if [ $? -ne 0 ]; then
echo "cmake failed"
exit 1
fi
make -jsudo apt-get install -y build-essential libevent-dev
# get XQUIC source code
git clone https://github.com/alibaba/xquic.git; cd xquic
# get and build BabaSSL(Tongsuo)
git clone -b 8.3-stable https://github.com/Tongsuo-Project/Tongsuo.git ./third_party/babassl; cd ./third_party/babassl/
./config --prefix=/usr/local/babassl
make -j
SSL_TYPE_STR="babassl"
SSL_PATH_STR="${PWD}"
cd -
# build XQUIC with BabaSSL
# When build XQUIC with babassl, /usr/local/babassl directory will be searched
# as default. If babassl is deployed in other directories, SSL_PATH could be
# used to specify the search path of babassl
git submodule update --init --recursive
mkdir -p build; cd build
cmake -DGCOV=on -DCMAKE_BUILD_TYPE=Debug -DXQC_ENABLE_TESTING=1 -DXQC_SUPPORT_SENDMMSG_BUILD=1 -DXQC_ENABLE_EVENT_LOG=1 -DXQC_ENABLE_BBR2=1 -DXQC_ENABLE_RENO=1 -DSSL_TYPE=${SSL_TYPE_STR} -DSSL_PATH=${SSL_PATH_STR} ..
# exit if cmake error
if [ $? -ne 0 ]; then
echo "cmake failed"
exit 1
fi
make -jsh ../scripts/xquic_test.sh-
For using the API, see the API docs.
-
For platform support details, see the Platforms docs.
-
For Chinese Simplified (zh-CN) translation of the IETF QUIC Protocol, see the Translation docs.
-
For using quic-qlog, see the Features: qlog
-
For testing the library, see the Testing docs.
-
For other frequently asked questions, see the FAQs and Trouble Shooting Guide.
We would love for you to contribute to XQUIC and help make it even better than it is today! All types of contributions are encouraged and valued. Thanks to all contributors. See our Contributing Guidelines for more information.
If you have any questions, please feel free to open a new Discussion topic in our discussion forums.
XQUIC is released under the Apache 2.0 License.
Feel free to contact us in the following ways:
-
e-mail: xquic@alibaba-inc.com
-
Dingtalk group: 34059705
-
slack channel: #xquic in quicdev group
