3. If a Chinese parameter is transferred from the. HTML file to the. Aspx file (that is, Url conversion is not performed using the Redirect () method from the background ). Similarly, the passed Chinese parameters must be encoded and decoded upon receiving.
> Transfer
<Script language = "JavaScript">
Function GoUrl ()
{
Var Name = "Chinese parameter ";
Location. href = "B. aspx? Name = "+ escape (Name );
}
</Script>
<Body onclick = "GoUrl ()">
> Receive
String Name = Request. QueryString ["Name"];
Response. Write (Server. UrlDecode (Name ));
In general. Set the web. config file. However, if you use JavaScript to call the webservice method (passing Chinese parameters to webservice ). The web. config file is invalid. -------------------- Coding and decoding in html: <script language = "javascript">
Function openUrl (src)
{
Var strUrl = escape (src );
Window. open (strUrl );
} Function change_url (src)
{
Document. location. href = escape (src );
} </Script> in the new window, save <a href = 'javascript: openUrl ("css/ .doc"); '> submit the contract </a> at the current location, without blinking. <A href = "#" onclick = BLOCKED SCRIPTchange_url ("css/ .doc")> contract </a> Note: The slash in the path is "/" instead of "\", otherwise, it will not work. ----------------------------------------
When I was developing a. net Web, I encountered a very strange problem, that is, in the Url, if the Chinese character is passed as the parameter value, the value of QueryString may be wrong. To put it simply, for example, the following Url:
UrlParmTest. aspx? Parm1 = China & parm2 = Chinese
In Request. QueryString, parm1 and parm2 get both "China". Obviously there is a problem, but in some cases it is normal.
If the request uses response. redirect instead of a url, no similar problems have been encountered.
At that time, I thought that the Chinese language was double-byte encoding. It was possible that there was uncertainty when it was passed, but it was still good to use English.
But why is redirect on the server normal? Where is the problem?
Yesterday I asked my colleagues at gtec about the following:
If you set Chinese parameters in the. cs file, Encode the Chinese parameters using Server. UrlEncode ("Chinese ").
If you set it in the. aspx file, use <% = Server. UrlEncode ("Chinese") %> to Encode
When QueryString is used, Decode is not required to obtain a normal Chinese string.
The following are some explanations:
UrlEncode converts several multi-byte characters into the single-byte characters allowed in the url, which will be automatically implemented by the browser. However, there are some problems, so Encode it yourself, the receiver automatically performs Decode on the Url.
I think Response. Redirect may be able to ensure the work of The Encode, so there is no problem.
Start building with 50+ products and up to 12 months usage for Elastic Compute Service
1 on 1 presale consultation
24/7 Technical Support 6 Free Tickets per Quarter Faster Response
Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.
A comprehensive suite of global cloud computing services to power your business
Payment Methods We Support
