blocks|key|1237924|text|尝试将以下内容添加到页面顶部：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1237925|<%25
Response.CharSet+=+"utf-8"
Session.CodePage+=+65001
%25>|code-block|syntax|javascript|1237926|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Try adding the following to the top of the page:

<pre><code>&lt;%
Response.CharSet = "utf-8"
Session.CodePage = 65001
%&gt;
</code></pre>

blocks|key|1216421|text|@本·邓纳普:在页面顶部试试这个--|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1216422|<%25@LANGUAGE="VBSCRIPT"+CODEPAGE="65001"%25>|code-block|syntax|javascript|1216423|更新|offset|length|style|BOLD|1216424|如果你做一个Response.Write+Request.Form("country")，它会显示什么？|CODE|1216425|entityMap^0|0|0|0|2|0|6|12|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|S|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|T|8|@$I|U|J|V|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|W|8|@$I|X|J|Y|K|O]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|Q|$]]

@Ben Dunlap: Try this at the top of the page --

<pre><code>&lt;%@LANGUAGE="VBSCRIPT" CODEPAGE="65001"%&gt;
</code></pre>

Update 
If you do a <code>Response.Write Request.Form("country")</code>, what does it display?

blocks|key|1237980|text|结果发现我走错了方向。所讨论的ASP文件本身是用UTF-8编码的，它隐式地将Response.CodePage设置为65001+--换句话说，显式添加CODEPAGE指令没有什么区别--事实上，UTF-8编码是问题的根源。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1237981|当我将文件重新编码到Windows1252时，问题消失了。总的来说，我对字符编码非常无知，但我认为回溯过去，帖子中的%25D6应该是我的线索--如果我开始正确地理解事物，单字节0xD6就不是一个有效的UTF-8字符。也许更熟悉这些事情的人可以证实或否认这一点。|1237982|entityMap^0|23|8|0|1M|3|2E|4|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

Turns out I was going the wrong direction with this. The ASP file in question was itself encoded in UTF-8, which was implicitly setting Response.CodePage to 65001 -- in other words, explicitly adding a <code>CODEPAGE</code> directive made no difference -- and in fact the UTF-8 encoding was the source of the problem.

When I re-encoded the file to Windows-1252, the problem disappeared. I'm pretty ignorant of character encodings in general, but I think in retrospect the <code>%D6</code> in the POST should have been my clue -- if I'm starting to understand things rightly, the single byte <code>0xD6</code> is not a valid UTF-8 character. Maybe someone more familiar with these things could confirm or deny this.

blocks|key|1216470|text|如果使用查询字符串中的Ascii字符0+(编码为(%2500)+)，我可以检索整个值而不被Ascii+0终止吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1216471|http://localhost/Test_Authentication.asp?token=%2513%2523%2502%2500%2501%2501%2500%2501%2501%2505%2502%2502%2503%2500%2502%2502%250A%250A%250A%250A%250A%250A048


Response.CharSet+=+"utf-8";
Session.CodePage=65001;

var+strToken+=+(Request.QueryString("token").Count+>+0)?Request.QueryString("token")(1):"";|code-block|syntax|javascript|1216472|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

What about using the Ascii Character 0 in the query string, encoded as (%00), can I retrieve the whole value without terminating by Ascii 0?

<pre><code>http://localhost/Test_Authentication.asp?token=%13%23%02%00%01%01%00%01%01%05%02%02%03%00%02%02%0A%0A%0A%0A%0A%0A048


Response.CharSet = "utf-8";
Session.CodePage=65001;

var strToken = (Request.QueryString("token").Count &gt; 0)?Request.QueryString("token")(1):"";
</code></pre>

blocks|key|1216492|text|我使用的两个简单步骤是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1216493|1216494|在每个asp文件的顶部添加：|ordered-list-item|1216495|1216496|Response.CharSet+=+"utf-8“|1216497|Response.CodePage+=65001|1216498|以"ANSI“编码保存每个|unordered-list-item|1216499|
|1216500|文本文件(不是utf-8!)+-此选项通常在高级文本编辑器|1216501|
的”保存“窗口中找到。|1216502|如果以utf-8编码方式保存，或者不添加代码顶部指定的两行代码，这将永远不会按您的意愿工作。|1216503|entityMap^0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|Z|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|11|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|12|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|13|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|14|8|@]|9|@]|A|$]]|$1|P|3|Q|5|M|7|15|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|16|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|17|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|W|$]]

The 2 simple steps I used were:

<ol>
<li>add at the top of EVERY asp file: 

Response.CharSet = "utf-8"

Response.CodePage = 65001</li>
<li>save every ASP text file in "ANSI" encoding (NOT utf-8!) - this option is usually found in the "Save" window of advanced text editors</li>
</ol>

If you save in utf-8 encoding or if you don't add the two line specified at the top of your code, this will never work as you intended.

blocks|key|101513|text|我的问题类似(但很奇怪)，在我的所有页面中添加以下两行已经更正了它。非常感谢你这么做。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|101514|Response.CharSet+=+"UTF-8"
Response.Codepage+=+65001|code-block|syntax|javascript|101515|但是，要解释的是，这是我的问题所在。人们在我的ASP条目页面上输入西班牙字符，结果非常奇怪。例如，输入了“Pe+a”。ASP页面将显示这一点，正如所输入的那样，但是数据库中的结果显示为"Pe?a“。这是可以的，除非数据库中存储的十六进制实际上是0x50653F6100。注意额外的"00”。数据库存储的值在结尾有一个额外的空值。所以，当我稍后检索到数据时，当"00“NULL被击中时屏幕变得有点疯狂，显示的数据在这些数据之后基本上停止了。|101516|在任何情况下，添加这两行似乎都解决了这个问题，并且“i”按其应有的方式存储在数据库中。|101517|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

My issue was similar (but quite strange) and adding the following two lines on all my pages has corrected it. Thanks so much for this.
<pre><code>Response.CharSet = &quot;UTF-8&quot;
Response.Codepage = 65001
</code></pre>
But, to explain, here is the exact issue I had. Folks were entering Spanish characters on my ASP entry page and the results were very weird. For example&quot; &quot;Peña&quot; was entered. The ASP page would display this, as entered, but what ended up in the database was displayed back as &quot;Pe?a&quot;. This would have been sort of ok, except the hex actually stored in the database was 0x50653F6100. Notice the extra &quot;00&quot;. Somehow the database stored value had an extra NULL at the end. So, when I later retrieved the data the screens went a little bonkers when the &quot;00&quot; [null] was hit and the displayed data essentially stopped after this data.
In any case adding the two lines seems to have fixed the issue and the &quot;ñ&quot; is stored in the database as it should be.

A client of mine is using a Classic ASP script to process a form from a third-party payment processor (this is the last step in a credit-card-transaction sequence that starts at the client's website, goes to the third-party site, and then returns to the client's site).

The client is in Austria and when one of the fields includes an 8-bit character (e.g., when the field value is Österreich), the Ö is simply dropped when I retrieve the value of the field in the standard way; e.g.:

<pre><code>fieldval = Request.Form("country")
If fieldval = "sterreich" Then
 ' Code here will execute
End If
</code></pre>

The literal value that the third-party page is POSTing is <code>%D6sterreich</code>, which I think suggests that the POST is being encoded in UTF-8.

The POST request has the following possibly-relevant headers:

<ul>
<li><code>Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7</code></li>
<li><code>Content-Type: application/x-www-form-urlencoded</code></li>
</ul>

I'm by no means a character-encoding expert and this is the first time I've really done anything with Classic ASP, so I'm kind of flummoxed.

From some Googling and searching SO, I've added the following to the page that processes the POST:

<pre><code>&lt;%@ Codepage=65001 %&gt;
&lt;%
Response.CharSet = "UTF-8"
Response.Codepage = 65001
%&gt;
</code></pre>

But it doesn't make any difference -- I still lose that initial 8-bit character. Is there something really simple that I'm just not aware of?

Classic ASP's Request.Form is dropping an 8-bit character -- is there a simple way to prevent this?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我的一个客户端正在使用一个经典的ASP脚本来处理来自第三方支付处理器的表单(这是信用卡交易序列中的最后一步，从客户的网站开始，转到第三方站点，然后返回到客户的站点)。客户端在奥地利，如果其中一个字段包含8位字符(例如，当字段值为sterreich时)，则在我以标准方式检索字段值时，只需删除该字段；例如：fieldval...

问经典的ASP的Request.Form正在删除一个8位字符--有一个简单的方法来防止这种情况发生吗？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问经典的ASP的Request.Form正在删除一个8位字符--有一个简单的方法来防止这种情况发生吗？EN