I'm experiencing the same error with Chromium, which is probably not any client to tell to go to hell.
This page contains the following errors:
error on line 2 at column 3: Char 0x0 out of allowed range Below is a rendering of the page up to the first error.
Presumably, a lot of WebKit-based browsers will fail with the same error. Safari anyone?
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] For every complex problem, there is a solution that is simple, neat, and wrong. — H. L. Mencken
Faré fahree@gmail.com writes:
I'm experiencing the same error with Chromium, which is probably not any client to tell to go to hell.
This page contains the following errors:
error on line 2 at column 3: Char 0x0 out of allowed range Below is a rendering of the page up to the first error.
Presumably, a lot of WebKit-based browsers will fail with the same error. Safari anyone?
http://www.weitz.de/hunchentoot? Works with Safari (4.0.4).
Nicolas
On Mon, Feb 8, 2010 at 5:01 AM, Nicolas Neuss neuss@math.uni-karlsruhe.de wrote:
Faré fahree@gmail.com writes:
I'm experiencing the same error with Chromium, which is probably not any client to tell to go to hell.
This page contains the following errors:
error on line 2 at column 3: Char 0x0 out of allowed range Below is a rendering of the page up to the first error.
Presumably, a lot of WebKit-based browsers will fail with the same error. Safari anyone?
http://www.weitz.de/hunchentoot? Works with Safari (4.0.4).
It's dependent on the encoding. If you interpret the page as utf-8, there's an encoding error (except I get it at line 2 column 54). If you interpret it as Windows-1252, it displays fine. Chrome 4.0.279.78 on Windows here.
~TJ
On 8 February 2010 08:58, Tab Atkins Jr. jackalmage@gmail.com wrote:
On Mon, Feb 8, 2010 at 5:01 AM, Nicolas Neuss neuss@math.uni-karlsruhe.de wrote:
Faré fahree@gmail.com writes:
I'm experiencing the same error with Chromium, which is probably not any client to tell to go to hell.
This page contains the following errors:
error on line 2 at column 3: Char 0x0 out of allowed range Below is a rendering of the page up to the first error.
Presumably, a lot of WebKit-based browsers will fail with the same error. Safari anyone?
http://www.weitz.de/hunchentoot? Works with Safari (4.0.4).
It's dependent on the encoding. If you interpret the page as utf-8, there's an encoding error (except I get it at line 2 column 54). If you interpret it as Windows-1252, it displays fine. Chrome 4.0.279.78 on Windows here.
So is the solution that said hunchentoot page should declare its encoding in HTTP headers?
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] If it's not worth doing right, it's not worth doing. — Scott McKay
Am 08.02.2010 um 16:10 schrieb Faré:
So is the solution that said hunchentoot page should declare its encoding in HTTP headers?
HTTP 1.1 defaults to ISO-8859-1 if no encoding is given within the headers.
The best solution for you is not to setup your browser to default to UTF-8 when there is no information on encoding because wishful thinking just doesn't work in the wilderness of the modern web ;-). Alternatively you can always scratch your head when you encounter encoding errors like this.
ciao, Jochen
On Mon, 2010-02-08 at 07:58 -0600, Tab Atkins Jr. wrote:
On Mon, Feb 8, 2010 at 5:01 AM, Nicolas Neuss neuss@math.uni-karlsruhe.de wrote:
Faré fahree@gmail.com writes:
I'm experiencing the same error with Chromium, which is probably not any client to tell to go to hell.
This page contains the following errors:
error on line 2 at column 3: Char 0x0 out of allowed range Below is a rendering of the page up to the first error.
Presumably, a lot of WebKit-based browsers will fail with the same error. Safari anyone?
http://www.weitz.de/hunchentoot? Works with Safari (4.0.4).
It's dependent on the encoding. If you interpret the page as utf-8, there's an encoding error (except I get it at line 2 column 54).
Hmm - over here that's how the page source looks:
<?xml version="1.0" encoding="ISO-8859-1"?> <?xml-stylesheet type="text/xsl" href="clixdoc.xsl" ?>
Decoding this as utf-8 can hardly be blamed on the webserver .... Oh, header is:
Date: Mon, 08 Feb 2010 15:30:31 GMT Server: Apache Last-Modified: Mon, 11 Jan 2010 12:36:29 GMT Etag: "2c0102-204d6-47ce2c953ad40" Accept-Ranges: bytes Content-Length: 132310 Content-Type: application/xml
200 OK
So, no explicit content-encoding, so default encoding (ISO-8859-1 iirc).
HTH Ralf Mattes
If you interpret it as Windows-1252, it displays fine. Chrome 4.0.279.78 on Windows here.
~TJ
tbnl-devel site list tbnl-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel
-
Faré -
Jochen Schmidt -
Nicolas Neuss -
Ralf Mattes -
Tab Atkins Jr.