According to Gabriele Bartolini:
> !?!?!?!?!? Sorry guys!
> 
> > > > >Header line: HTTP/1.1 200 OK
> 
> >The very odd thing with these header lines is there is no space or
> >tab between the colon after the header name, and before the value.
> >I've never seen this before, and from my reading of the RFCs, this
> >isn't allowed in HTTP/1.0.  It turns out it is allowed by HTTP/1.1,
> >where you can have any amount of white space, or none at all, but not
> >in 1.0, which requires a single space after the ":".
> 
> I'll give it a look and eventually hack the code asap for the 3.2.x branch, 
> by the end of the week. What about the 3.1.x?

The patch I posted yesterday was for 3.1.6.  I never actually tested it,
but based on my understanding of the code it should solve this problem.

Oliver, we'd appreciate some feedback to know for sure if the patch works.
Also make sure that your htdig/Document.cc hasn't been hacked to send
out the GET request using HTTP/1.1, as I've seen from some bug reports
from 3.1.x.  Seeing the htdig -vvv output above the "Header line: " output,
where the GET command is shown, should confirm that your htdig client is
doing the right thing.

For 3.2, I think making the same change to the code in
HtHTTP::ParseHeader(), around line 660 in htnet/HtHTTP.cc, will fix it up.

-- 
Gilles R. Detillieux              E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre       WWW:    http://www.scrc.umanitoba.ca/
Dept. Physiology, U. of Manitoba  Winnipeg, MB  R3E 3J7  (Canada)


-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a 
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html

Reply via email to