Opened 15 years ago

Last modified 7 years ago

#65 closed defect (Fixed)

Mirroring dir via apache introduces unrecognized x-compress header

Reported by: arma Owned by:
Priority: Low Milestone: 0.0.9.3
Component: Core Tor/Tor Version: 0.0.9.2
Severity: Keywords:
Cc: arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Jan 15 16:18:42.480 [warn] parse_http_response(): Unrecognized content encoding: 'x-compress'
Jan 15 16:18:42.480 [warn] router_get_hash_impl(): couldn't find "signed-directory"
Jan 15 16:18:42.480 [warn] router_parse_routerlist_from_directory(): Unable to compute digest of directory
Jan 15 16:18:42.480 [warn] router_load_routerlist_from_directory(): Couldn't parse directory.
Jan 15 16:18:42.480 [warn] connection_dir_client_reached_eof(): I failed to parse the directory I fetched from 62.116.124.106:80. Ignoring.

Is this as simple as teaching Tor about x-compress?

Is there a workaround whereby we can get people to rig their apaches
to use x-deflate or x-gzip (that is, let the headers through from the
proxied connection) despite apache's default?

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (3)

comment:1 Changed 14 years ago by nickm

This isn't a Tor problem, it's an Apache problem: Apache sees the .z url that we are using to clue Tor that we want a deflated file, and deduces that the file is clearly compressed with LZW, which libz doesn't handle.

The solution is to make Tor better able to handle nonsensical content-encoding headers.

comment:2 Changed 14 years ago by nickm

flyspray2trac: bug closed.

comment:3 Changed 7 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.