Blair Zajac <[EMAIL PROTECTED]> writes:

> Gisle Aas wrote:
> > 
> > But I still think the goal should be to make the HTTP/1.1 driver good
> > enough for real use against bad servers.
> 
> OK.  Here's the patch to fix this behavior.  It's a tiny one against
> Net::HTTP.

Thanks!

I'm not sure this patch is good enough.  If we find bad headers I
think we should stop reading header lines or you might get stuck
reading from a server that never outputs an empty line.

Should probably force a "Connection: close" header in this case also
so that we don't try to send multiple request on this connection.

I guess there should be a limit on how many header lines and how long
header lines we accept to read anyhow.

> How often do you put out new versions of libwww-perl to fix these issues?

Whenever I feel there are enough accepted patches to make a new
release worthwhile.  You can also get LWP from CVS at SourceForge if
you want tolive on the bleading edge.

Regards,
Gisle

> +++ HTTP.pm   Tue Nov 13 20:10:37 2001
> @@ -7,7 +7,7 @@
>  use strict;
>  use vars qw($VERSION @ISA);
>  
> -$VERSION = "0.03";
> +$VERSION = "0.04";
>  eval { require IO::Socket::INET } || require IO::Socket;
>  @ISA=qw(IO::Socket::INET);
>  
> @@ -267,7 +267,7 @@
>           $headers[-1] .= " " . $line;
>       }
>       else {
> -         die "Bad header: $line\n";
> +         push(@headers, 'Client-Bad-Header-Line', $line);
>       }
>      }
>      return @headers;

Reply via email to