Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
N
nghttp2
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Libraries
nghttp2
Commits
d7af5924
Commit
d7af5924
authored
Oct 10, 2021
by
Tatsuhiro Tsujikawa
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
nghttpx: Extend QUIC server ID to 4 bytes
parent
a48e9d3d
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
6 additions
and
6 deletions
+6
-6
doc/sources/nghttpx-howto.rst
doc/sources/nghttpx-howto.rst
+3
-3
src/shrpx.cc
src/shrpx.cc
+2
-2
src/shrpx_quic.h
src/shrpx_quic.h
+1
-1
No files found.
doc/sources/nghttpx-howto.rst
View file @
d7af5924
...
...
@@ -544,10 +544,10 @@ Algorithm described in `QUIC-LB draft
<https://datatracker.ietf.org/doc/html/draft-ietf-quic-load-balancers>`_.
A Connection ID that nghttpx generates is always 20 bytes long. It
uses first 2 bits as a configuration ID. The remaining bits in the
first byte are reserved and random. The next
2
bytes are server ID.
The next
6
bytes are used to route UDP datagram to a correct
first byte are reserved and random. The next
4
bytes are server ID.
The next
4
bytes are used to route UDP datagram to a correct
``SO_REUSEPORT`` socket. The remaining bytes are randomly generated.
The server ID and the next 1
4
bytes are encrypted with AES-ECB. The
The server ID and the next 1
2
bytes are encrypted with AES-ECB. The
key is derived from the keying materials stored in a file specified by
:option:`--frontend-quic-secret-file`. The first 2 bits of keying
material in the file is used as a configuration ID. The remaining
...
...
src/shrpx.cc
View file @
d7af5924
...
...
@@ -3395,8 +3395,8 @@ HTTP/3 and QUIC:
Specify server ID encoded in Connection ID to identify
this particular server instance. Connection ID is
encrypted and this part is not visible in public. It
must be
2
bytes long and must be encoded in hex string
(which is
4
bytes long). If this option is omitted, a
must be
4
bytes long and must be encoded in hex string
(which is
8
bytes long). If this option is omitted, a
random server ID is generated on startup and
configuration reload.
--no-quic-bpf
...
...
src/shrpx_quic.h
View file @
d7af5924
...
...
@@ -64,7 +64,7 @@ struct QUICKeyingMaterials;
struct
QUICKeyingMaterial
;
constexpr
size_t
SHRPX_QUIC_SCIDLEN
=
20
;
constexpr
size_t
SHRPX_QUIC_SERVER_IDLEN
=
2
;
constexpr
size_t
SHRPX_QUIC_SERVER_IDLEN
=
4
;
// SHRPX_QUIC_CID_PREFIXLEN includes SHRPX_QUIC_SERVER_IDLEN.
constexpr
size_t
SHRPX_QUIC_CID_PREFIXLEN
=
8
;
constexpr
size_t
SHRPX_QUIC_CID_PREFIX_OFFSET
=
1
;
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment