Marten Seemann 9608e8563f only accept 3 retries ...

While the server is allowed to perform multiple Retries, the client
should impose a limit in order to avoid being caught in an endless loop.

2018-08-14 18:35:25 +07:00

..

connection_id_test.go

always use connection IDs longer than 8 bytes when sending a Retry

2018-08-14 17:34:21 +07:00

connection_id.go

always use connection IDs longer than 8 bytes when sending a Retry

2018-08-14 17:34:21 +07:00

encryption_level_test.go

make the protocol package internal

2017-08-30 00:19:44 +07:00

encryption_level.go

make the protocol package internal

2017-08-30 00:19:44 +07:00

packet_number_test.go

use varint packet numbers in IETF QUIC headers

2018-06-06 16:07:47 +02:00

packet_number.go

use varint packet numbers in IETF QUIC headers

2018-06-06 16:07:47 +02:00

perspective_test.go

also use the multiplexer for the server

2018-08-08 10:03:22 +07:00

perspective.go

also use the multiplexer for the server

2018-08-08 10:03:22 +07:00

protocol_suite_test.go

make the protocol package internal

2017-08-30 00:19:44 +07:00

protocol_test.go

implement the recent changes to the version negotiation packet

2017-12-06 08:40:43 +07:00

protocol.go

implement parsing of headers with different connection ID lengths

2018-07-03 18:01:41 +07:00

server_parameters.go

only accept 3 retries

2018-08-14 18:35:25 +07:00

stream_id_test.go

implement sending of MAX_STREAM_ID frames

2018-02-06 08:32:16 +08:00

stream_id.go

implement sending of MAX_STREAM_ID frames

2018-02-06 08:32:16 +08:00

version_test.go

use varint packet numbers in IETF QUIC headers

2018-06-06 16:07:47 +02:00

version.go

use varint packet numbers in IETF QUIC headers

2018-06-06 16:07:47 +02:00