aboutsummaryrefslogtreecommitdiff
path: root/internal/ui/static/js/modal_handler.js (follow)
AgeCommit message (Collapse)AuthorFilesLines
2024-03-20Replace a bunch of `let` with `const`Gravatar jvoisin 1-7/+7
According to https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/const > Many style guides (including MDN's) recommend using const over let whenever a variable is not reassigned in its scope. This makes the intent clear that a variable's type (or value, in the case of a primitive) can never change.
2023-08-10Move internal packages to an internal folderGravatar Frédéric Guillot 1-0/+101
For reference: https://go.dev/doc/go1.4#internalpackages
lue='search'/>
path: root/src (unfollow)
AgeCommit message (Collapse)AuthorFilesLines
2021-05-21stream: undo consistent RangeBuf allocation on sendGravatar Alessandro Ghedini 2-109/+25
Currently, when writing stream data, `RangeBuf` objects are allocated with a fixed capacity, and if the buffer is not immediately filled, the next stream write will re-use it. This was originally implemented to try to reduce memory fragmentation of stream data, and, in order to be able to maintain the `Send` and `Sync` traits implementation, the `RangeBuf` data buffer was wrapped in an `RWlock`, in order to implement thread-safe interior mutability. However due to the fact that the locking falls within 2 hot code paths (stream data writing, and STREAM frame creation) it heavuily affects throughput. In retrospect, the benefit of reduced memory fragmentation does not seem to justify the performance penalty, so this undoes the consistent allocation change to remove the need for the lock. This partially reverts commit 0976433e68ea1926aa9cf581e1a5846aba6da672.
2021-05-18calculate max CRYPTO frame length more accuratelyGravatar Alessandro Ghedini 1-27/+32
Instead of using a static value of what the frame overhead _could_ be, use the actual header length value that is available.
2021-05-17ffi: expose source / destination connection IDsGravatar Norman Maurer 2-0/+27
Motivation: We should expose functions to access the source and destination ids via the c API as well Modifications: Expose functions in the C API Result: Be able to access the ids of a connection
2021-05-12stop sending packets if drainingGravatar Alessandro Ghedini 1-0/+11
This check is currently done in `Connection::send()` as well, but when coalescing multiple packets, if one causes the connection to move to draining (e.g. because a CONNECTION_CLOSE was sent), we should stop trying to write additional coalesced packets.
2021-05-12add PADDING frame to fill up the datagram with Initial packetGravatar Junho Choi 1-9/+58
For Initial packets we need to make the UDP datagram at least 1200 bytes following the transport spec. However when the last packet in the datagram is Short and the datagram is not fully filled, we try to do null padding at the end which causes a decryption failure on the server because Short packet doesn't have an explicit length. To avoid this issue, when Short packet is added in the same datagram with Initial packet, add a PADDING frame to Short packet to fill up the datagram size. If Short packet is not added, we still add zero padding at the end of packet.
2021-05-12cubic: fast convergence from the rfc8312bis draftGravatar Junho Choi 1-12/+69
Update based on https://github.com/NTAP/rfc8312bis/pull/35 - remove w_last_max - update the logic of fast convergence - fix the bug where fast convergence is not applied
2021-05-12cubic: AIMD approach for TCP friendly windowGravatar Junho Choi 1-25/+47
- Update based on https://github.com/NTAP/rfc8312bis/pull/24 - Fix congestion avoidance test
2021-05-12cubic: redefine K equation according to the rfc8312bis draftGravatar Junho Choi 1-16/+34
- Update based on https://github.com/NTAP/rfc8312bis/pull/3 - Fix congestion avoidance test (but still has a TODO)
2021-05-12h3: make quiche_h3_recv_dgram signature consistentGravatar Lucas Pardue 1-1/+2
Seems we missed the header file...
2021-05-11use PAYLOAD_LENGTH_LEN constGravatar Junho Choi 1-1/+1
2021-05-10validate protocol version when creating ConfigGravatar Norman Maurer 1-0/+25
Motivation: We should validate that the version is valid that was used to create the Config object and if not fail. Modifications: - Add validation for the version - Add some tests Result: Version is validated during config creation
2021-05-06apps: fix inconsistent struct constructorGravatar Alessandro Ghedini 1-1/+1
2021-05-06apps: use parse() to convert string to intGravatar Alessandro Ghedini 1-8/+8
2021-05-06qlog: use map() instead of pattern matchingGravatar Alessandro Ghedini 1-15/+3
2021-05-06h3: use parse() to convert string to intGravatar Alessandro Ghedini 1-3/+6
2021-05-06ffi: expose client-side session resumption and 0-RTT APIGravatar Norman Maurer 2-0/+33
Motivation: Quiche added support for session resumption and 0-RTT lately but the API was not exposed via the C api. This was done in https://github.com/cloudflare/quiche/pull/911 and https://github.com/cloudflare/quiche/pull/914. Modifications: Add C API to also be able to make use of the functionality via C. Result: Be able to use session resumption and 0-RTT via the C api
2021-05-05check the packet length against the buffer sizeGravatar Junho Choi 1-1/+70
When we queue 0-rtt packets in undecryptable_pkts, there is a case that actual packet length is smaller than the size in the payload (packet length field) which may cause a runtime panic. Such packet is undecryptable in any way, so check it early and return error.