Re: [PATCH] Default charset patch (bug 0000068)

Paul P Komkoff Jr wrote:

> Replying to Stipe Tolj:
> 
>>the behaviour of libcurl and gwlib's http.c?
> 
> 
> Yes. curl doesn't mangle headers in any way.

hm... As I noticed, the section reading from the HTTP/1.1 RFC is more like "this 
is what the server should do", IMO. So the question is if it is up to the 
server, then obiously out gwlib/http client module does "too much" from the role 
of the server. If we interpret it this way, it's up to the maintainer of the 
application served by the HTTP server to ensure that HTTP headers do reflect 
correct content-type charset encoding headers.

I'm not quite sure. What would you mean reading the refenrenced section of RFC 2616?

In terms of libcurl support, this would mean, we would have to check 
"afterwards" if this symptom is given and recode the charset like we do four our 
own gwlib/http, right?

Stipe

mailto:stolj_{at}_wapme.de
-------------------------------------------------------------------
Wapme Systems AG

Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany

phone: +49.211.74845.0
fax: +49.211.74845.299

mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
-------------------------------------------------------------------