Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #25676

Closed (moved)
Open
Opened Mar 29, 2018 by teor@teor

When a client asks for a gzip-encoded consensus, the server sends zlib

$ curl -s -O --header "Accept-Encoding: gzip" 91.121.230.208:9030/tor/status-vote/current/consensus && file consensus
Accept-Encoding: gzip
Requested: status-vote/current/consensus
consensus: zlib compressed data

But when the client asks for gzip-encoded descriptors, the server sends gzip:

Accept-Encoding: gzip
Requested: server/authority
authority: gzip compressed data, max compression, from Unix

See https://trac.torproject.org/projects/tor/ticket/25667#comment:11 for a full list of requested encodings, documents, and served formats.

I think this is a minor bug with no impact, because tor clients will decompress the zlib anyway. (I don't know if tor clients ever ask for gzip without zlib.)

But I'd like someone who knows the compression code better to confirm.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#25676