We have http://www.bnk.ca/~conversation turning up gibberish.

Yet I do check on http://www.nk.ca/index.html.jp and nothing
is wrong. What is happening?
--
Member - Liberal International
This is doctor@nl2k.ab.ca Ici doctor@nl2k.ab.ca
God Queen and country! Beware Anti-Christ rising!
Arsenal Ahead to win the UEFA CL 2005/2006

The Doctor wrote:
> We have http://www.bnk.ca/~conversation turning up gibberish.

Guessing the corrections for two typos in that URL gives me:
Content-Type: text/html; charset=ISO-8859-1

> Yet I do check on http://www.nk.ca/index.html.jp and nothing
> is wrong. What is happening?

Well that's a page in English from here. I guess that's because
I don't accept japanese in my browser preferences. I'd also
guess that the japanese version of it contains the correct charset
header, perhaps due to a configuration file entry for .jp.

--
Nick Kew

On Sun, 14 May 2006, Nick Kew wrote:

[quoting a reference to an erroneous URL which presumably should
have been http://www.nk.ca/~conversation/ ...]

Yup, the server is adding charset=iso-8859-1 on the HTTP Content-type
header, as you said. O.P needs to read and understand, for example,
http://www.w3.org/International/O-HTTP-charset

> > Yet I do check on http://www.nk.ca/index.html.jp and nothing
> > is wrong. What is happening?
>
> Well that's a page in English from here.

I get a 302 redirect to http://www.nk.ca/index.shtml , which indeed is
in English (and iso-8859-1 encoded). (And rudely forcing a pixel
width which refuses to fit in my regular browser window - lame design
- but I suppose that's for another forum. "Failed validation - 102
errors", and the CSS is little better).

A temporary redirect to this misbegotten page seems to be their
server's response to any URL that they didn't understand. Pity
someone hasn't taught them about use of HTTP 4xx status codes, with
custom error body, for reporting erroneous URLs.

> I guess that's because I don't accept japanese in my browser
> preferences.

I see what you're getting at, but there's no Vary: header in the
response, so either there's no server-side negotiation going on, or -
if there *is* something - it's botched.

I tried adding jp to my languages prefs, but it made no difference.

> I'd also guess that the japanese version of it contains the correct
> charset header, perhaps due to a configuration file entry for .jp.

The observations seem to me to be so out of alignment with the
original question, that I'm not convinced that we're looking at the
same page as the questioner intended.

On Sun, 14 May 2006, Nick Kew wrote:

[quoting a reference to an erroneous URL which presumably should
have been http://www.nk.ca/~conversation/ ...]

Yup, the server is adding charset=iso-8859-1 on the HTTP Content-type
header, as you said. O.P needs to read and understand, for example,
http://www.w3.org/International/O-HTTP-charset

> > Yet I do check on http://www.nk.ca/index.html.jp and nothing
> > is wrong. What is happening?
>
> Well that's a page in English from here.

I get a 302 redirect to http://www.nk.ca/index.shtml , which indeed is
in English (and iso-8859-1 encoded). (And rudely forcing a pixel
width which refuses to fit in my regular browser window - lame design
- but I suppose that's for another forum. "Failed validation - 102
errors", and the CSS is little better).

A temporary redirect to this misbegotten page seems to be their
server's response to any URL that they didn't understand. Pity
someone hasn't taught them about use of HTTP 4xx status codes, with
custom error body, for reporting erroneous URLs.

> I guess that's because I don't accept japanese in my browser
> preferences.

I see what you're getting at, but there's no Vary: header in the
response, so either there's no server-side negotiation going on, or -
if there *is* something - it's botched.

I tried adding jp to my languages prefs, but it made no difference.

> I'd also guess that the japanese version of it contains the correct
> charset header, perhaps due to a configuration file entry for .jp.

The observations seem to me to be so out of alignment with the
original question, that I'm not convinced that we're looking at the
same page as the questioner intended.

In article <Pine.LNX.4.64.0605141306200.2834@ppepc20.ph.gla.a c.uk>,
Alan J. Flavell <flavell@physics.gla.ac.uk> wrote:
>On Sun, 14 May 2006, Nick Kew wrote:
>
>[quoting a reference to an erroneous URL which presumably should
>have been http://www.nk.ca/~conversation/ ...]
>
>Yup, the server is adding charset=iso-8859-1 on the HTTP Content-type
>header, as you said. O.P needs to read and understand, for example,
>http://www.w3.org/International/O-HTTP-charset
>

Got you.

>> > Yet I do check on http://www.nk.ca/index.html.jp and nothing
>> > is wrong. What is happening?
>>
>> Well that's a page in English from here.
>
>I get a 302 redirect to http://www.nk.ca/index.shtml , which indeed is
>in English (and iso-8859-1 encoded). (And rudely forcing a pixel
>width which refuses to fit in my regular browser window - lame design
>- but I suppose that's for another forum. "Failed validation - 102
>errors", and the CSS is little better).
>
>A temporary redirect to this misbegotten page seems to be their
>server's response to any URL that they didn't understand. Pity
>someone hasn't taught them about use of HTTP 4xx status codes, with
>custom error body, for reporting erroneous URLs.
>
>> I guess that's because I don't accept japanese in my browser
>> preferences.
>
>I see what you're getting at, but there's no Vary: header in the
>response, so either there's no server-side negotiation going on, or -
>if there *is* something - it's botched.
>
>I tried adding jp to my languages prefs, but it made no difference.
>
>> I'd also guess that the japanese version of it contains the correct
>> charset header, perhaps due to a configuration file entry for .jp.
>
>The observations seem to me to be so out of alignment with the
>original question, that I'm not convinced that we're looking at the
>same page as the questioner intended.

Hmm! As for http://ww.nk.ca/ I think I will point the above out to the
designer.
--
Member - Liberal International
This is doctor@nl2k.ab.ca Ici doctor@nl2k.ab.ca
God Queen and country! Beware Anti-Christ rising!
Arsenal Ahead to win the UEFA CL 2005/2006

In article <Pine.LNX.4.64.0605141306200.2834@ppepc20.ph.gla.a c.uk>,
Alan J. Flavell <flavell@physics.gla.ac.uk> wrote:
>On Sun, 14 May 2006, Nick Kew wrote:
>
>[quoting a reference to an erroneous URL which presumably should
>have been http://www.nk.ca/~conversation/ ...]
>
>Yup, the server is adding charset=iso-8859-1 on the HTTP Content-type
>header, as you said. O.P needs to read and understand, for example,
>http://www.w3.org/International/O-HTTP-charset
>

Got you.

>> > Yet I do check on http://www.nk.ca/index.html.jp and nothing
>> > is wrong. What is happening?
>>
>> Well that's a page in English from here.
>
>I get a 302 redirect to http://www.nk.ca/index.shtml , which indeed is
>in English (and iso-8859-1 encoded). (And rudely forcing a pixel
>width which refuses to fit in my regular browser window - lame design
>- but I suppose that's for another forum. "Failed validation - 102
>errors", and the CSS is little better).
>
>A temporary redirect to this misbegotten page seems to be their
>server's response to any URL that they didn't understand. Pity
>someone hasn't taught them about use of HTTP 4xx status codes, with
>custom error body, for reporting erroneous URLs.
>
>> I guess that's because I don't accept japanese in my browser
>> preferences.
>
>I see what you're getting at, but there's no Vary: header in the
>response, so either there's no server-side negotiation going on, or -
>if there *is* something - it's botched.
>
>I tried adding jp to my languages prefs, but it made no difference.
>
>> I'd also guess that the japanese version of it contains the correct
>> charset header, perhaps due to a configuration file entry for .jp.
>
>The observations seem to me to be so out of alignment with the
>original question, that I'm not convinced that we're looking at the
>same page as the questioner intended.

Hmm! As for http://ww.nk.ca/ I think I will point the above out to the
designer.
--
Member - Liberal International
This is doctor@nl2k.ab.ca Ici doctor@nl2k.ab.ca
God Queen and country! Beware Anti-Christ rising!
Arsenal Ahead to win the UEFA CL 2005/2006