为什么重音符号在不同的URL访问同一服务器上的同一code当渲染不一致? [英] Why are accented characters rendering inconsistently when accessing the same code on the same server at a different URL?

查看:151
本文介绍了为什么重音符号在不同的URL访问同一服务器上的同一code当渲染不一致?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

有就是我们的服务器上的页面,通过两个不同的URL的访问。

There is a page on our server that's reachable via two different URLs.

http://www.spotlight.com/6213-5613-0721

http://www.spotlight.com/interactive/cv/1/ M103546.html

有传统的ASP在幕后,无一不这些URL实际上做一个Server.Transfer的相同的基础ASP页。

There's classic ASP behind the scenes, and both of those URLs actually do a Server.Transfer to the same underlying ASP page.

在页面顶部的名称中的重音在一个URL正确渲染,并错误地在其他 - 但据我所知,这两个请求返回相同的反应(相同的标记,同样的标题,同样一切的) - 和我完全不知道为什么一个网址,要正确渲染,而另一种是破坏重音字符

The accents in the name at the top of the page are rendering correctly on one URL and incorrectly on the other - but as far as I can tell, the two requests are returning identical responses (same markup, same headers, same everything) - and I have absolutely no idea why one URL should be rendering correctly whilst the other is corrupting the accented characters.

还有什么(内容编码?)我应该检查 - ?如果是这样,我怎么能知道什么东西被退回超出萤火虫显示的信息

Is there anything else (content encoding?) that I should be examining - and if so, how can I tell what's being returned beyond the information displayed in Firebug?

推荐答案

我一直在这个问题在过去,问题是,一些文件(也许ASP文件做转让或部分包括)不被保存为ANSI

I been in this problem in the past and the problem was that some file (maybe the asp file that do the transfer or some include) is not saved as ANSI.

检查涉及的要求的所有文件具有相同的编码服务器(试行文件 - >另存为编码)

Check that all files involved in the request has the same encoding in the server (try File -> Save As With Encoding)

这篇关于为什么重音符号在不同的URL访问同一服务器上的同一code当渲染不一致?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆