<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hey guys, <div class=""><br class=""></div><div class="">Probably nobody saw this because of the time of year (Happy New Year, incidentally!!!).</div><div class=""><br class=""></div><div class="">Just a quick ping to the list to see if anyone can give me some pointers. </div><div class=""><br class=""></div><div class="">Chris</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 30 Dec 2015, at 12:15 PM, Chris Sherlock <<a href="mailto:chris.sherlock79@gmail.com" class="">chris.sherlock79@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">Hi guys,<div class=""><br class=""></div><div class="">In bug 95217 - <a href="https://bugs.documentfoundation.org/show_bug.cgi?id=95217" class="">https://bugs.documentfoundation.org/show_bug.cgi?id=95217</a> - Persian test in a webpage encoded as UTF-8 is corrupting.</div><div class=""><br class=""></div><div class="">If I take the webpage and save to an HTML file encoded as UTF8, then there are no problems and the Persian text comes through fine. However, when connecting to a webserver directly, the HTTP header correctly gives the content type as utf8.</div><div class=""><br class=""></div><div class="">I did a test using Charles Proxy with its SSL interception feature turned on and pointed Safari to <a href="https://bugs.documentfoundation.org/attachment.cgi?id=119818" class="">https://bugs.documentfoundation.org/attachment.cgi?id=119818</a></div><div class=""><br class=""></div><div class="">The following headers are gathered:</div><div class=""><br class=""></div><div class=""><pre class="bz_comment_text" id="comment_text_7" style="font-size: inherit; width: 50em;">HTTP/1.1 200 OK
Server: nginx/1.2.1
Date: Sat, 26 Dec 2015 01:41:30 GMT
Content-Type: text/html; name="text.html"; charset=UTF-8
Content-Length: 982
Connection: keep-alive
X-xss-protection: 1; mode=block
Content-disposition: inline; filename="text.html"
X-content-type-options: nosniff</pre></div><br class=""><div class="">Some warnings are spat out that it editeng's eehtml can't detect the encoding. I initially thought it was looking for a BOM, which makes no sense for a webpage, but that's wrong. Instead, for some reason the headers don't seem to be processed and the HTML parser is falling back to ISO-8859-1 and not UTF8 as the character encoding.</div><div class=""><br class=""></div><div class="">We seem to use Neon to make the GET request to the webserver. A few observations:</div><div class=""><br class=""></div><div class="">1. We detect a server OK response as an error</div><div class="">2. (Probably more to the point) I believe PROPFIND is being used, but actually even though the function being used indicates a PROPFIND verb is used a GET is used as is normal but the headers aren't being stored. This ,Evans that when the parser looks for the headers to find the encoding it's not finding anything, resulting in a fallback to ISO-8859-1.</div><div class=""><br class=""></div><div class="">One easy thing (doesn't solve the root issue) is that wouldn't it be a better idea to fallback to UTF8 and not ISO-8859-1, given ISO-8859-1 is really just a subset of UTF-8?</div><div class=""><br class=""></div><div class="">Any pointers on how to get to the bottom of this would be appreciated, I'm honestly not up on webdav or Neon.</div><div class=""><br class=""></div><div class="">Chris Sherlock</div>
</div></blockquote></div><br class=""></div></body></html>