summaryrefslogtreecommitdiff
path: root/examples/with-vue/src/components
diff options
context:
space:
mode:
authorGravatar Tony @ Navillus <60468564+tony-navillus@users.noreply.github.com> 2021-06-28 13:22:15 +0200
committerGravatar GitHub <noreply@github.com> 2021-06-28 06:22:15 -0500
commitaa8605761b0758a9ca0a0963393b92c74eb39466 (patch)
tree329c85ad5273b99383fb9ae901ed5fce93193187 /examples/with-vue/src/components
parent11cf22999d9eeb45d25596af481d8bc27fa931ec (diff)
downloadastro-aa8605761b0758a9ca0a0963393b92c74eb39466.tar.gz
astro-aa8605761b0758a9ca0a0963393b92c74eb39466.tar.zst
astro-aa8605761b0758a9ca0a0963393b92c74eb39466.zip
Fix collections regex (#557)
* fix: :bug: Fixes bug #532 Matching for collection routes should look for exact filename matches * test: :white_check_mark: Adding test coverage to make sure collection routes are matched exactly * chore: Adding changeset
Diffstat (limited to 'examples/with-vue/src/components')
0 files changed, 0 insertions, 0 deletions
generated by cgit v1.2.3 (git 2.46.0) at 2025-10-17 10:11:02 +0000
pan class='deletions'>-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.