begin_dir broken on 0.1.2.13?

I finally got tunneled connections working correctly for clients.

It works great when connecting to 0.2.0.x servers. But when connecting to 0.1.2.13, it fetches a lot of directory info over the TLS connection, but it gets an EOF early:

Apr 27 06:28:38.980 [debug] fetch_from_buf_http(): headerlen 141, bodylen 151383 . Apr 27 06:28:38.981 [debug] connection_dir_client_reached_eof(): Received respon se from directory server '86.59.21.38:443': 200 "OK" Apr 27 06:28:38.981 [debug] connection_dir_client_reached_eof(): Time on receive d directory is within tolerance; we are -9 seconds skewed. (That's okay.) Apr 27 06:28:38.997 [info] tor_gzip_uncompress(): possible truncated or corrupt zlib data Apr 27 06:28:38.997 [info] connection_dir_client_reached_eof(): Unable to decomp ress HTTP body (server '86.59.21.38:443'). Apr 27 06:28:38.998 [debug] conn_close_if_marked(): Cleaning up connection (fd - 1). Apr 27 06:28:38.998 [info] connection_dir_request_failed(): Giving up on directo ry server at '86.59.21.38'; retrying

Whereas on moria, it works:

Apr 27 06:29:36.305 [debug] fetch_from_buf_http(): headerlen 141, bodylen 471545 . Apr 27 06:29:36.306 [debug] connection_dir_client_reached_eof(): Received respon se from directory server '18.244.0.114:443': 200 "OK" Apr 27 06:29:36.306 [debug] connection_dir_client_reached_eof(): Time on receive d directory is within tolerance; we are -9 seconds skewed. (That's okay.) Apr 27 06:29:36.352 [info] connection_dir_client_reached_eof(): Received network status objects (size 1063662) from server '18.244.0.114:443' Apr 27 06:29:36.417 [debug] check_directory_signature(): Signed directory hash s tarts F2FF957E

Is this a bug with 0.2.0's linked connections? Or a bug with 0.1.2.13's handling of begin_dir?

[Automatically added by flyspray2trac: Operating System: All]