Dealing with "http format error"

[Tollef Fog Heen]

]] Jay Luker 

| After continuing to debug my problem I've had to reassess what the
| actual issue is. Again, the request URL I'm trying to proxy is this:
| 
| http://nedwww.ipac.caltech.edu/cgi-bin/nph-objsearch?z_unit=z&z_value1=&z_value2=&radius=9.99996&zv_breaker=30000.0&hconst=73&omegam=0.27&out_equinox=J2000.0&list_limit=5&in_equinox=J2000.0&lon=05+23+34.6&in_csys=Equatorial&omegav=0.73&obj_sort=Distance+to+search+center&corr_z=1&out_csys=Equatorial&img_stamp=NO&lat=-69+45+22&ot_include=ANY&of=ascii_bar&nmp_op=ANY&z_constraint=Unconstrained&search_type=Near+Position+Search
| 
| It appears that because this backend does not provide any http headers
| in the response that varnish is interpreting part of the response
| itself as the protocol, status code, etc. The log output below
| indicates that the RxProtocol, RxStatus, RxResponse and RxHeader
| values actually contain strings from what should be the body of the
| response.

Seems like your backend is speaking HTTP 0.9, which I'm not sure we
support.  Is there any chance you could get it to be less archaic?

-- 
Tollef Fog Heen
Varnish Software
t: +47 21 54 41 73