Gisle Aas wrote:
> What do you think it should do? We could have the Content-type in the
> <head> always override the content-type in the response headers, but
> that might throw out information and I don't like that. We could have
> LWP not override the header, but then you often loose the extra
> charset parameter that is often what is added in this <head> version
> of the header. The current way might give you surprises, but it does
> not throw away information.
That's true, but it sure breaks the standard. I think the most sensible
thing to do is to overwrite the headers with content from the <head>
section, as this is just what the <head> section is intended for.
For security, a overwrite_headers option could be added, so worried
users can disable this behavior.
--
Pazu
