Hrvoje Niksic wrote:
> 2) Server messages printed by Wget in normal operation, such as the
> "200 Ok" message. That one is printed just for the "fun factor"
> anyway, we could as well print just the response code. However, I
> don't see a problem with simply filtering out the non-ASCII's from
> the response code. People who put non-ASCII messages in server
> response lines won't be able to see them properly in Wget's output,
> but I honestly couldn't care less.
Those messages are using Latin 1. HTTP/1.0 worked that way and it was not
changed in HTTP/1.1 for compatibility reasons. I don't expect that
non-ASCII characters are used much, though. I've only seen the status
messages translated to French, once.
The Warning header carries text intended for the user and it's the only
such header, AFAIK. Again, text defaults to Latin 1 and the usual MIME-ish
complications can be used for other character sets.
--
.-. .-. Yes, I am an agent of Satan, but my duties are largely
(_ \ / _) ceremonial.
|
| [EMAIL PROTECTED]
