mirrors/arti.git/crates/tor-dirclient/src/request.rs, branch arti-v1.1.13 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.13 2024-01-08T18:19:11Z Fix typos 2024-01-08T18:19:11Z Dimitris Apostolou dimitris.apostolou@icloud.com 2024-01-04T18:32:22Z urn:sha1:4eb54be0657862f5d56b047c16c08dabde6a7377 Only send Content-Length when needed. 2023-11-27T14:38:00Z Nick Mathewson nickm@torproject.org 2023-11-27T14:38:00Z urn:sha1:babebf2a9dc471c8de4bde0cc81e7f2c4c0aafff According to RFC 9110: A user agent SHOULD send Content-Length in a request when the method defines a meaning for enclosed content and it is not sending Transfer-Encoding. For example, a user agent normally sends Content-Length in a POST request even when the value is 0 (indicating empty content). A user agent SHOULD NOT send a Content-Length header field when the request message does not contain content and the method semantics do not anticipate such data. Part of #1024 tor-dirclient: Always set the Content-Length header. 2023-10-24T14:42:35Z Gabriela Moldovan gabi@torproject.org 2023-10-24T12:05:34Z urn:sha1:7ae30d9ca63c5b2ec8675374d5a686972a3c4965 dirclient: Seal the Requestable trait and hide most of its members. 2023-10-17T13:39:31Z Nick Mathewson nickm@torproject.org 2023-10-17T13:39:31Z urn:sha1:7fef9b468a2e3f730ee510eff3d29c98606f1a73 Since none of these methods were invoked from outside `tor-dirclient` (except for debugging), and since we have had a fair amount of churn on what we actually want them to be, it seems like a good idea to use this trick to hide them. This will let us make other changes to the actual behavior of Requestable in the future. dirclient: Rename partial_docs_ok to partial_response_body_ok 2023-10-17T13:17:07Z Nick Mathewson nickm@torproject.org 2023-10-17T13:17:07Z urn:sha1:c850a5d400df240c8e088afa36ca119b2601ca30 dirclient: Make Requestable::anonymized mandatory. 2023-10-17T13:14:04Z Nick Mathewson nickm@torproject.org 2023-10-17T13:14:04Z urn:sha1:69b5c13985fbe122e785dffb52fff6b38603978d dirclient: Explain why 1024 is a sufficient maximum response length. 2023-10-16T18:57:59Z Nick Mathewson nickm@torproject.org 2023-10-16T18:57:59Z urn:sha1:f3761e2afcc99c2298a4102631a467dada47ad6a dirclient: Wrap a somewhat wide comment. 2023-10-16T18:57:29Z Nick Mathewson nickm@torproject.org 2023-10-16T18:57:29Z urn:sha1:a3fb3d2802768a948ff0dd0a32e3570e77d85624 Downgrade another TODO HSS and move it to TODO BREAKING 2023-10-16T18:53:46Z Nick Mathewson nickm@torproject.org 2023-10-16T18:53:46Z urn:sha1:0b3e15e344ca359f6ae846b286297709dc1e0f6b Privacy: Do not list supported encodings in hsdesc reqs. 2023-10-16T18:49:41Z Nick Mathewson nickm@torproject.org 2023-10-16T18:32:39Z urn:sha1:cfe641613e6b6f4f55de87621eadacf24d22a939 Since not everybody has xz and/or zstd, we don't want to admit whether we support them when we are uploading or downloading an onion service descriptor. Similarly, if we aren't advertising support for an encoding, we shouldn't accept it. Finally, while we're doing this, it made sense to have the ability to mark requests based on how anonymized they are, and reject (some) attempts to send those requests over a one-hop circuit. Closes #1062