From 626b2a13c8ffdc70a382a8e7ebcf8eea02cf5a8f Mon Sep 17 00:00:00 2001 From: "Edward Z. Yang" Date: Thu, 5 Jul 2007 16:50:48 +0000 Subject: [PATCH] Typographical and linkrot fixes for UTF-8 doc. git-svn-id: http://htmlpurifier.org/svnroot/htmlpurifier/trunk@1308 48356398-32a2-884e-a903-53898d9a118a --- docs/enduser-utf8.html | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/enduser-utf8.html b/docs/enduser-utf8.html index ef8c136b..b8cee57d 100644 --- a/docs/enduser-utf8.html +++ b/docs/enduser-utf8.html @@ -231,7 +231,7 @@ of your real encoding.

why the character encoding should be explicitly stated. When the browser isn't told what the character encoding of a text is, it has to guess: and sometimes the guess is wrong. Hackers can manipulate - this guess in order to slip XSS pass filters and then fool the + this guess in order to slip XSS past filters and then fool the browser into executing it as active code. A great example of this is the Google UTF-7 exploit.

@@ -567,10 +567,11 @@ which may be used by POST, and is required when you want to upload files.

The following is a summarization of notes from - + FORM submission and i18n. That document contains lots of useful information, but is written in a rambly manner, so -here I try to get right to the point.

+here I try to get right to the point. (Note: the original has +disappeared off the web, so I am linking to the Web Archive copy.)

application/x-www-form-urlencoded