"John Byrne" <Jo*******@discussions.microsoft.com> wrote in message
news:14**********************************@microsof t.com...
"Ray Costanzo [MVP]" wrote: "John Byrne" <Jo*******@discussions.microsoft.com> wrote in message
news:D2**********************************@microsof t.com...
This is an ASP Request object problem. Different browser makes no
difference.
Not necessarily.
Did you miss the part where I asked if the à appears in a view-source?
If so, it's a browser problem. I'm not saying that this is the problem,
but it'd help to rule it out...
Ray at work
This is certainly a server-side issue. If the URL for a page is ?parm=AAà
and the ASP page did:
Response.Write(Request.QueryString);
you get:
parm=AAà
but if you did:
Response.Write(Request("parm"));
you get:
AA
but works fine if page invoke via a form (either post or get)
JB
Actually, it's probablly a combination of both client and server issues. I
believe the problem is associated with the character encoding. Here are some
things to check:
1. In your browser, what character encoding are you using?
2. On the server, what codepage/character encoding are being used. There are
quite a few places where codepage can be set. Here's an excerpt from the
Response.CodePage documentation that describes how the codepage setting
cascades:
If Response.CodePage is not explicitly set in a page, it is implicitly set
by Session.CodePage, if sessions are enabled. If sessions are not enabled,
Response.CodePage is set by @CodePage, if @CodePage is present in the page.
If there is no @CodePage in the page, Response.CodePage is set by the
AspCodePage metabase property. If the AspCodePage metabase property is not
set, or set to 0, Response.CodePage is set by the system ANSI codepage.
Here's a link to the documentation:
http://www.msdn.microsoft.com/librar...om_resopcp.asp