rust-websocket-lite
rust-websocket-lite copied to clipboard
A fast, low-overhead WebSocket client
Bumps [tokio-util](https://github.com/tokio-rs/tokio) from 0.7.1 to 0.7.2. Commits 038de36 chore: prepare tokio-util 0.7.2 (#4690) 42d5a9f Merge 'tokio-util-0.6.x' into 'tokio-util-0.7.x' cdb132d Revert "chore: disable warnings in old CI (#4691)" 2659adf chore: prepare...
Right now, the maximum frame size is hardcoded (https://github.com/1tgr/rust-websocket-lite/blob/master/websocket-codec/src/frame.rs#L53) and extremely high, making maliciously long frames possible, allowing attackers to rapidly use up memory on the receiving side. The same...
Hi Tim, I've done the following things: * lint the whole project against clippy's pedantic level and fix the issues (a couple `#[must_use]`, missing error sections in docs, possible truncations...
``` Compiling websocket-lite v0.5.0 error[E0432]: unresolved import `self::inner` --> /Users/afpro/.cargo/registry/src/github.com-1ecc6299db9ec823/websocket-lite-0.5.0/src/ssl.rs:87:15 | 87 | pub use self::inner::*; | ^^^^^ could not find `inner` in `self` error[E0425]: cannot find function `async_wrap` in...
This PR adds an optional size limit to the `MessageCodec`, which allows server to prevent clients from sending large messages that could cause the server to run out of memory.
Hi, The README on this repo says "You can use this crate in both asynchronous (futures-based) and synchronous code.". I suppose that's technically true, but it doesn't really hint that...
Mentioned by @bluetech on ba1f935f250b8249f2581d0620784c0f45fc737a: https://github.com/1tgr/rust-websocket-lite/blob/ba1f935f250b8249f2581d0620784c0f45fc737a/websocket-codec/src/upgrade.rs#L118 > This function is not exactly right; it will also accept e.g. `Upgrade2` but it shouldn't. > > To be fully pedantic, the websocket...
After initial buffers are allocated (or allocating a buffer on the stack), assert that no memory is allocated or freed to transmit or receive single-frame messages.
- ~`impl Encoder for UpgradeCodec`~ probably not, as the web framework will handle sending of headers for the Upgrade request - Integration with relevant web framework(s): - [x] hyper -...