Scamper already looks at the response code, and completely ignores the
human readable comment (because Scamper is not a human).

I've looked at the problem, and it appears it's due to the web server's
non-compliance with HTTP RFC (I still need to check more). RFC specifies
CRLF to be the end of line marker (inside header, and for separator
between header/footer - double CRLF). However,the server seems to be
sending UNIX EOL character.

Netscape/IE are probably more forgiving (and thus non-compliant) to this
and many other issues.

Bolot


On Mon, 21 Jun 1999, Michael Donegan wrote:

> >From the HTTP 1.1 RFC:
> 
> The individual values of the numeric status codes defined for
>    HTTP/1.1, and an example set of corresponding Reason-Phrase's, are
>    presented below. The reason phrases listed here are only recommended
>    -- they may be replaced by local equivalents without affecting the
>    protocol.
> 
> A client should look at the 200 and not the message. The message is for
> some human to read.
> 
>         mkd
>