lucy24 - 9:15 am on Sep 2, 2013 (gmt 0)
The browser is not requesting ò
What does the <img src... say? ò or %C3%B2?
Ugh, that would be horrible. f2 is a flat-out forbidden character in UTF-8, so that would be an even worse error than misinterpreting UTF8 as 8859-1.
:: google, google ::
Are we on Tomcat by any chance?
By default, Tomcat uses ISO-8859-1 character encoding when decoding URLs received from a browser. This can cause problems
... Yes, indeed. It says here [confluence.atlassian.com] (really https, but forums refused to cooperate)
<Connector port="8090" URIEncoding="UTF-8"/>
which of course is so much Hungarian to me, but it's one of the few pages I found that even understands the question; most turn out to be about file encoding within an html document, not the URL. Curiously, Tomcat seems to be a recurring theme among those that do know what's going on. Also java, which is not much help.
Here is another useful if infuriating [blog.lunatech.com] version from a few years back:
The standards do not define any way by which a URI might specify the encoding it uses, so it has to be deduced from the surrounding information. For HTTP URLs it can be the HTML page encoding, or HTTP headers. This is often confusing and a source of many errors. In fact, the latest version of the URI standard defines that new URI schemes use UTF-8
Thanks. Just what we needed to hear.
And then there's this [freecode.com], which strikes me as a throwing-in-the-towel approach, but may actually work. (Full disclosure: I found the link on That Other Forum.)