mirrors/arti.git/crates/tor-dirserver/src/http.rs, branch arti-v2.5.1

Much formatting churn for 2024 edition

2026-07-22T12:25:53Z

Remove now-unneeded allow(clippy::cognitive_complexity)

2026-07-15T18:05:29Z

maint: Run maint/add_warning to deny string slices

2026-06-09T15:36:01Z

This commit executes maint/add_warning with the just added change to deny string slices except in tests. I recommend auditing this by checking out the previous commit followed by running the script yourself and then verifying that the diff is identical to this commit. This commit makes cargo clippy fail. We will add exceptions in the next commit.

Fix typos

2026-03-24T16:04:08Z

Typos found with codespell

dirserver: Allow clippy::unused_async

2026-01-27T19:11:05Z

This code is still WIP, no need to address the lint yet.

tor-dirserver: Remove FromStr for DocumentId

2026-01-22T15:20:19Z

This commit removes FromStr for DocumentId because it was only used in testing anyways. Instead, it replaces it with a simple From<[u8; 32]> only enabled in test builds, which is sufficient for what we are trying to do. An alternative would be to make the inner field pub, but this seems to aggressive for a testing only thing.

tor-dirserver: Rename `doc_id` to `docid`

2026-01-19T10:01:59Z

Because we went with `docid` in the database (due to `rowid`), it is only natural to call the code variables `docid` too.

tor-dirserver: Rename sha256 to docid in schema

2026-01-19T10:01:59Z

This commit renames the sha256 column to docid for the reason that we agreed upon making the schema visible to all modules, so if we were to encapsulate docid properly, this change is only natural.

database: Introduce DocumentId

2026-01-19T10:01:59Z

This commit introduces a new type in the database module named `DocumentId` for abstracting the underlying content-addressable hash algorithm we are using.

tor-dirserver: Move ContentEncoding to database

2026-01-15T10:49:14Z

This commit moves the ContentEncoding enum from the http module to the database module, primarily because the content encoding is more of a matter to the database, as this is where the data actually resides.