Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

14
  • 8
    @LarsViklund I should have been clearer with my comment. I meant that the validation associated with character encoding is simplified, not bypassed. Commented Oct 13, 2012 at 13:48
  • 3
    @Lars Correct, it doesn't absolve you from having to check your input. But it does mean that encoding tweaks only become part of your security handling and don't taint the concept of your "standard processing" path Commented Oct 14, 2012 at 10:08
  • 40
    Also see stackoverflow.com/questions/3222013/…. Apparently Ruby on Rails used to use a snowman character, and was changed to a checkmark which was less ambiguous but less funny. Commented Oct 17, 2012 at 10:06
  • 11
    @JohnLBevan it's ignored by the receiving end, it's done it's job to force the browser to send things in utf8 instead of latin1. I've also seen it as ie=💩 (that's the 'pile of poo' code point, looks like it's not rendering in comments.) Commented Oct 18, 2012 at 19:54
  • 3
    @Gareth: Can you back-up the statement that IE <= 8 forms do not support the document and/or form encoding? Commented Oct 22, 2012 at 13:00