mirrors/arti.git/crates/tor-proto/src/stream/incoming.rs, branch arti-v1.2.2

Rename the old IncomingStreamRequestContext to StreamReqInfo.

2024-03-26T16:55:05Z

(Doing this to prevent us having two structs with the same name.)

Add an IncomingStreamRequestFilter to check early properties

2024-03-26T16:55:05Z

Based on designs in #1124. Note that there is a TODO here about a hack I had to do to appease the borrow checker.

Run maint/add_warning.

2024-03-13T16:30:53Z

relay-cell: Update relay cell decoding API for prop340

2024-03-12T15:58:12Z

Prop 340: https://spec.torproject.org/proposals/340-packed-and-fragmented.html This updates the decoding API to support multiple versions of the relay cell encoding, including the new encoding proposed in prop340 that supports relay message packing and fragmentation. This commit doesn't actually add support for that new encoding yet.

Rename UnparsedRelayCell -> UnparsedRelayMsg

2024-03-12T15:58:12Z

For consistency with the terminology proposed in https://gitlab.torproject.org/tpo/core/torspec/-/issues/253

tor_cell: never construct empty DATA messages.

2024-02-13T14:37:11Z

We never actually constructed these before, but now we enforce it at the API level. Part of #1269.

Rename {Any}RelayCell to {Any}RelayMsgOuter

2023-12-14T16:56:58Z

This commit is pure renaming, done automatically with rust-analyzer. Comment fixes and other cleanups will be in the subsequent commits. We're doing this renaming because we need a name for the combination of a `RelayMsg` and an `Option` that we use when we have a `RelayMsg` we intend to route to a given stream or circuit internally. Previously we called this a `RelayCell`, but that name was already somewhat inaccurate, and will become _very_ inaccurate with the arrival of prop340, which breaksthe 1:1 relationship between relay cells and relay messages. (If we didn't do this renaming now, we'd soon be making the relationship between `UnparsedRelayCell`and `RelayCell` many-to-many, which would be ridiculous and confusing.) The `RelayMsgOuter` name is a placeholder: We expect that we'll want to rename this type, and may also want to rename `RelayMsg`, and unify our vocabulary in other areas too. But such a renaming will have to wait for a larger discussion affecting the specifications, so that we can use the same vocabulary everywhere.

Convert StreamId to NonZeroU16

2023-10-25T20:34:55Z

proto: Revise the behavior of IncomingStream::discard().

2023-10-19T17:15:10Z

Because dropping a `StreamTarget` causes the circuit reactor to send an End, the previous do-nothing implementation of `discard()` wasn't sufficient to cause the request to be ignored without sending an End. This commit modifies our "close pending stream" behavior to only optionally send an End message. To avoid confusion, I'm using a new `CloseStreamBehavior` enum rather than an `Option`, since we had previously used `None` in some cases to indicate a default (misc) end message.

IncomingStream:: flatten IncomingStreamInner.

2023-10-19T17:15:10Z