Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 316
    • Issues 316
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 36
    • Merge requests 36
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #25676
Closed
Open
Created 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
Time tracking