Opened 12 years ago

Last modified 7 years ago

#539 closed defect (Fixed)

Dirservers give 503 response, but include content anyway.

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

Description

Reported on frell2 by packbart. The server is running 0.1.2.18.

packbart@hendrek:~$ telnet 85.10.240.250 80
Trying 85.10.240.250...
Connected to 85.10.240.250.
Escape character is '^]'.
GET /tor/server/d/C13519E867FB6761FC90A1CEA1E628817B18EE9E+C5532C1E1D73F578A6C8E88D4365A61334820DBD+5E1920509A6B5C64C754EE7CE371249DDBE643F3+93EC21BD7AD05AF61829657E415CA9DF5ACD9D69.z HTTP/1.0
Host: 85.10.240.250

HTTP/1.1 503 Directory busy, try again later
Date: Wed, 31 Oct 2007 21:01:19 GMT
Vary: Accept-Encoding
X-Cache: MISS from www.anon-proxy.de
Connection: close
Content-Type: text/plain; charset=iso-8859-1
Content-Encoding: x-compress

router videoraptor 88.198.67.4 9003 0 9032
platform Tor 0.1.1.26 on Linux i686
published 2007-10-31 19:00:52
opt fingerprint 5F47 51CE 3E98 4306 B520 32DF 1CE5 1A67 F118 7C9F
uptime 4349911
bandwidth 92160 131072 112693
onion-key


MIGJAoGBAMF4Ut+axDUHZGVDzOm613YQ7e1Js0T1BKZR55fzK+XUqSHd9sFveH9R
MUsu0U/YLW6pSi/NGZyb8T4B8+JF1ehsUhcJF2Qz4HbZlvYT7x/j85PwN7l+/hze
TobTi6H9d6W1Nh6jNeHPmVPlYemGG/oOR0w43EIt0OrGM7z6fLhhAgMBAAE=


signing-key


MIGJAoGBAMsEyOXG/RRht13cHiEmJgJ1+rn1Y5tldYTZzlMpv8m5ms9T2n2TB3BF

[...]

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (6)

comment:1 Changed 12 years ago by nickm

I think I got this fixed in r12882; the fix is backported as r12883. The bug should be fixed in 0.2.0.13-alpha and
in 0.1.2.19.

comment:2 Changed 12 years ago by arma

While this bug is still common in deployed servers, we should teach clients to
look at their body if they get a "503 busy". My client just spent 4 minutes
trying to bootstrap from a dir cache that slowly fed it 250KB, 996 bytes per second,
only to get a 503 at the end and so my client abandoned everything it had fetched.

comment:3 Changed 12 years ago by arma

(It's only critical to make clients better at this once we start them using
their fallback consensus, so requests to slow caches could be in the critical
path for startup. But we'd like to do that in the 0.2.0.x timeframe I think?)

comment:4 Changed 12 years ago by nickm

Client behavior fixed in r13054; backported in r13055.

comment:5 Changed 12 years ago by nickm

flyspray2trac: bug closed.

comment:6 Changed 7 years ago by nickm

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