Comment 7 for bug 40329
Revision history for this message
| Björn Tillenius (bjornt) wrote Re: [Bug 40329] Re: The wrong encoding is chosen if '*' is in the Accept-Charset header, but 'utf-8' isn't | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
On Mon, Apr 24, 2006 at 02:16:07PM -0000, Stuart Bishop wrote:
> I think we need to ignore the header entirely, always emitting UTF-8.
> If we emit pages in a charset other than UTF-8, then the client will
> submit forms with an encoding other than UTF-8 which will generate
> exceptions or cause us to store corrupted data.
Well, If we send the page as ISO-8859-1 the user will send us data
encoded as ISO-8859-1, and everything will be fine. We decode the POST
data using the same encoding we will send that page in. I'm not sure what
will happen if the user tries to POST non-ISO-8859-1 characters, though.
Anyway, I agree that we should ignore the header and always send UTF-8.
I think that will cause us and the users the least amount of problems.