ISSUE-31 - Public View
invalid bytes and default character encoding
- State:
- CLOSED
- Product:
- XMLHttpRequest
- Raised by:
- Anne van Kesteren
- Opened on:
- 2006-02-24
- Description:
During the Oslo F2F the following text was discussed: Otherwise, returns the body of the data received so far, interpreted using the character encoding specified in the response, or UTF-8 if no character encoding was specified. Invalid bytes must be converted to U+FFFD REPLACEMENT CHARACTER. ... several people suggested that instead of UTF-8 we should probably state ISO-8859-1 (per RFC2616?) and that "invalid bytes" should be clarified.
- Related emails:
- ISSUE-31: invalid bytes and default character encoding (from dean+cgi@w3.org on 2006-02-24)
- ISSUE-31: default encoding in XHR (from annevk@opera.com on 2006-04-04)
- Re: ISSUE-31: default encoding in XHR (from annevk@opera.com on 2006-04-04)
- Re: ISSUE-31: default encoding in XHR (from jonas@sicking.cc on 2006-04-04)
- Re: ISSUE-31: default encoding in XHR (from annevk@opera.com on 2006-04-04)
- Re: ISSUE-31: default encoding in XHR (from jonas@sicking.cc on 2006-04-05)
- Re: ISSUE-31: default encoding in XHR (from jonas@sicking.cc on 2006-04-05)
- ISSUE-31: default character encoding XHR (from annevk@opera.com on 2006-04-21)
- Re: ISSUE-31: default encoding in XHR (from annevk@opera.com on 2006-04-24)
- Re: ISSUE-31: default encoding in XHR (from jonas@sicking.cc on 2006-04-24)
- Open issues for XMLHttpRequest (from annevk@opera.com on 2006-05-01)
Note: Some of these links may be accessible only to W3C Members.
Related notes:
2006-05-16: Solved. See also ACTION-148.