乱码问题对每个程序员来说,都是曾经的一个伤疤。尤其是做J2EE的新手,这问题总在我们周围晃悠。起初是表单提交到action中乱码(最后到数据库当然是乱码),表面上看可能是数据库编码设置问题,但当我们正确设置数据库编码后仍然发现最后还是乱码,接着又认为是页面编码设置不统一而导致提交表单后出现乱码,这个火星人都知道,结果问题依然存在。这时我们又想到可能是提交时post到服务器导致的乱码,也正确,于是我们想到了将字符串转码。问题也能解决,但不能说每次提交我们都要将字符串转码吧,如果是这样,可能谁都不想干coding这行了,光花在这上面的时间,就虚度了大半光阴。后来,我们知道有了过滤流这玩意,所有乱码问题顿时成为往事。加个过滤器搞定一切乱码,从此我们不再烦恼。顿时想起“奇强”牌某某粉,过滤流==奇强。
正当我们以为不会再被乱码头疼的时候。ajax技术兴起了,那个爽啊,玩的不亦乐乎。ajax中经常用到url来传递参数,中文参数的更是用的日趋广泛。搞个ajax检索,需要吧,用了google的搜索她们都说好,我们能不用吗,怎么说也不能落后于潮流吧。新技术来了,老毛病也来了。在GBK GB2312编码的页面中使用ajax, 用url传递参数,结果提交的都是乱码。难道过滤流毛病了?这个不想做过多评论.问题总要想办法解决,网络中惊呼"url中传递参数乱码如何解决啊?","url中传递参数避免乱码的方案"。我只想说一句,"问题总能解决"。
废话够了,转如正题.
比如ajax请求的url="searchPeoBySomeWords.do?KeyWord="+obj.value;我们需要用escape函数来将中文参数“包装”两下,看清楚是两下,不是一下。url="searchPeoBySomeWords.do?KeyWord="+escape(escape(obj.value))。那么这样“包装”后我们如何在action中来解码了,不要急,一个java方法就能解决问题(代码如Escape.java)。action中我们只要用Escape.java中的unescape静态方法就可解码。String keyWord = Escape.unescape(request.getParameter("KeyWord")).trim();原来拆开"包装"后,依然是我们可爱的中文。
java 代码
- package com.ctgusec.oaPlus;
-
-
-
-
-
-
- public class Escape{
- private final static String[] hex = {
- "00","01","02","03","04","05","06","07","08","09","0A","0B","0C","0D","0E","0F",
- "10","11","12","13","14","15","16","17","18","19","1A","1B","1C","1D","1E","1F",
- "20","21","22","23","24","25","26","27","28","29","2A","2B","2C","2D","2E","2F",
- "30","31","32","33","34","35","36","37","38","39","3A","3B","3C","3D","3E","3F",
- "40","41","42","43","44","45","46","47","48","49","4A","4B","4C","4D","4E","4F",
- "50","51","52","53","54","55","56","57","58","59","5A","5B","5C","5D","5E","5F",
- "60","61","62","63","64","65","66","67","68","69","6A","6B","6C","6D","6E","6F",
- "70","71","72","73","74","75","76","77","78","79","7A","7B","7C","7D","7E","7F",
- "80","81","82","83","84","85","86","87","88","89","8A","8B","8C","8D","8E","8F",
- "90","91","92","93","94","95","96","97","98","99","9A","9B","9C","9D","9E","9F",
- "A0","A1","A2","A3","A4","A5","A6","A7","A8","A9","AA","AB","AC","AD","AE","AF",
- "B0","B1","B2","B3","B4","B5","B6","B7","B8","B9","BA","BB","BC","BD","BE","BF",
- "C0","C1","C2","C3","C4","C5","C6","C7","C8","C9","CA","CB","CC","CD","CE","CF",
- "D0","D1","D2","D3","D4","D5","D6","D7","D8","D9","DA","DB","DC","DD","DE","DF",
- "E0","E1","E2","E3","E4","E5","E6","E7","E8","E9","EA","EB","EC","ED","EE","EF",
- "F0","F1","F2","F3","F4","F5","F6","F7","F8","F9","FA","FB","FC","FD","FE","FF"
- };
- private final static byte[] val = {
- 0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,
- 0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,
- 0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,
- 0x00,0x01,0x02,0x03,0x04,0x05,0x06,0x07,0x08,0x09,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,
- 0x3F,0x0A,0x0B,0x0C,0x0D,0x0E,0x0F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,
- 0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,
- 0x3F,0x0A,0x0B,0x0C,0x0D,0x0E,0x0F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,
- 0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,
- 0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,
- 0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,
- 0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,
- 0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,
- 0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,
- 0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,
- 0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,
- 0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F,0x3F
- };
- public static String escape(String s) {
- StringBuffer sbuf = new StringBuffer();
- int len = s.length();
- for (int i = 0; i < len; i++) {
- int ch = s.charAt(i);
- if (ch == ' ') {
- sbuf.append('+');
- } else if ('A' <= ch && ch <= 'Z') {
- sbuf.append((char)ch);
- } else if ('a' <= ch && ch <= 'z') {
- sbuf.append((char)ch);
- } else if ('0' <= ch && ch <= '9') {
- sbuf.append((char)ch);
- } else if (ch == '-' || ch == '_'
- || ch == '.' || ch == '!'
- || ch == '~' || ch == '*'
- || ch == '\'' || ch == '('
- || ch == ')') {
- sbuf.append((char)ch);
- } else if (ch <= 0x007F) {
- sbuf.append('%');
- sbuf.append(hex[ch]);
- } else {
- sbuf.append('%');
- sbuf.append('u');
- sbuf.append(hex[(ch >>> 8)]);
- sbuf.append(hex[(0x00FF & ch)]);
- }
- }
- return sbuf.toString();
- }
- public static String unescape(String s) {
- StringBuffer sbuf = new StringBuffer();
- int i = 0;
- int len = s.length();
- while (i < len) {
- int ch = s.charAt(i);
- if (ch == '+') {
- sbuf.append(' ');
- } else if ('A' <= ch && ch <= 'Z') {
- sbuf.append((char)ch);
- } else if ('a' <= ch && ch <= 'z') {
- sbuf.append((char)ch);
- } else if ('0' <= ch && ch <= '9') {
- sbuf.append((char)ch);
- } else if (ch == '-' || ch == '_'
- || ch == '.' || ch == '!'
- || ch == '~' || ch == '*'
- || ch == '\'' || ch == '('
- || ch == ')') {
- sbuf.append((char)ch);
- } else if (ch == '%') {
- int cint = 0;
- if ('u' != s.charAt(i+1)) {
- cint = (cint << 4) | val[s.charAt(i+1)];
- cint = (cint << 4) | val[s.charAt(i+2)];
- i+=2;
- } else {
- cint = (cint << 4) | val[s.charAt(i+2)];
- cint = (cint << 4) | val[s.charAt(i+3)];
- cint = (cint << 4) | val[s.charAt(i+4)];
- cint = (cint << 4) | val[s.charAt(i+5)];
- i+=5;
- }
- sbuf.append((char)cint);
- }
- i++;
- }
- return sbuf.toString();
- }
-
-
-
-
-
-
- }
分享到:
相关推荐
了解这些基本概念后,结合以上三种方法,我们可以有效解决ASP.NET中URL参数传递中文时的乱码问题。在实际开发中,应根据具体项目需求和环境选择合适的方法,确保数据的正确传递。同时,为了兼容更多情况,建议在开发...
当我们需要在两个页面间通过URL传递参数时,经常会遇到中文乱码问题。这个问题主要是因为URL中的参数可能没有经过正确的编码和解码处理。为了解决这个问题,我们可以采取一些方法,特别是当使用jQuery来获取URL参数...
### AJAX传递中文参数乱码解决办法 在Web开发过程中,数据传输是不可或缺的一部分,而AJAX作为一种无需重新加载整个页面的情况下就能与服务器交换数据的技术,被广泛应用于动态数据交互场景中。然而,在处理中文等...
### extjs前后台交互参数出现中文乱码问题的解决方法 #### 问题背景与原因分析 在使用MyEclipse开发工具进行Web应用开发时,尤其是采用ExtJS框架结合Ajax技术进行前后端数据交互的过程中,可能会遇到一个常见的...
本文将详细介绍两种解决JSP页面URL参数乱码的方法,虽然不能保证100%有效,但它们是实践中常用且有效的解决方案。 **方法一:修改Tomcat配置** 1. 首先,我们需要进入Tomcat服务器的配置目录,通常是`$CATALINA_...
在IT领域,尤其是在Web开发中,处理URL传递参数时遇到中文乱码是一个常见的问题,尤其当数据需要跨系统或在不同编码环境下传输时更为显著。本文将深入探讨URL传参数时中文乱码的原因、影响以及如何有效解决这一问题...
总的来说,处理URL中传递的中文参数时,合理使用`encodeURI`和对应的解码方法,结合理解浏览器和服务器的编码行为,是避免乱码的关键。本文提供的“前端两次encode——后端一次decode”方案,是一种兼容性好且相对...
在Asp.Net开发中,遇到页面通过URL参数传递中文字符时出现乱码是一个常见的问题。这个问题通常是由于字符编码不一致导致的。以下是三种常见的解决方法: 1. **配置Web.config文件**: 在Web.config文件的`...
在IT行业中,Ajax(Asynchronous JavaScript ...通过理解和应用这些解决方案,开发者可以有效地避免和解决Ajax请求中的中文乱码问题,从而提高用户体验。记住,良好的编码习惯和对字符编码的理解是解决此类问题的关键。
本文将深入探讨如何解决JavaScript(简称JS)在传递中文字符时出现的乱码问题,并提供具体的解决方案。 #### 一、问题背景 在Web应用中,前端页面与后端服务之间通过HTTP请求进行数据交互是非常常见的操作。当这些...
然而,在实际操作中,我们时常会遇到一个问题,那就是当JSP页面通过URL传递包含中文字符的参数时,可能会出现乱码现象。这个问题主要源于HTTP协议的特性以及字符编码的处理不当。本教学视频将详细讲解如何解决JSP中...
尽管上述方法通常能解决大部分乱码问题,但为了避免不必要的麻烦,最好还是遵循“最好不要在URL中传递中文参数”的原则。因为URL可见且易于复制,如果包含敏感信息(如中文用户名),可能会增加隐私泄露的风险。另外...
本篇将详细介绍如何解决JSP传值过程中出现的中文乱码问题。 首先,我们需要理解乱码产生的原因。在网页中,数据的编码和解码过程需要保持一致。如果服务器和客户端之间使用的字符编码不同,就可能出现乱码。例如,...
本文将深入探讨“奇数个中文字符URL传递乱码”的问题,并提供一种可行的解决方案。 ### 一、问题背景 #### 1.1 URL编码概述 URL(Uniform Resource Locator)用于标识互联网上的资源位置。由于某些字符在URL中具有...
### AJAX技术使用XMLHttpRequest对象传递参数的中文乱码问题 #### 背景与问题概述 在使用AJAX技术进行前后端数据交互时,经常会出现中文字符编码的问题,尤其是在使用`XMLHttpRequest`对象发送请求的过程中。例如...
二、传递参数中文乱码解决 在jsp页面中,传递参数时也可能出现中文乱码问题。解决方法是修改Tomcat的server.xml文件,添加URLEncoding=”utf-8”参数,以指定Tomcat的编码方式为UTF-8。例如:“8080” protocol=...
URL传值到Action乱码解决方案 在Web应用程序中,URL传值到Action是一个常见的操作,但是当传递中文参数时,经常会出现乱码问题。今天,我们将讨论如何解决URL传值到Action乱码问题,特别是在Struts2框架中。 乱码...
在C++中,进行HTTP文件上传到Web服务器时,可能会遇到中文参数乱码的问题。这是因为HTTP协议本身并不处理字符编码,而是依赖于上层的应用层协议(如HTTP头或者POST数据)来处理字符集。当涉及到非ASCII字符,如中文...
在 JSP 开发中,中文乱码问题是一个常见的问题,本文总结了 JSP 中中文乱码问题的解决方法,希望能够帮助正在烦恼中文乱码的人。 一、JSP 页面显示乱码 JSP 文件页面显示乱码是一种很常见的问题,这种情况比较好...
在JSP开发中,处理URL编码传递中文参数是常见的需求,尤其是在构建动态网页时。这个问题主要涉及到字符编码的转换,因为不同的编码标准可能导致乱码。以下是对这个主题的详细解释: 1. **URL编码**:URL(统一资源...