utf-8和xhtml 1.0严格 [英] utf-8 and xhtml 1.0 strict
问题描述
我的网站自2003年4月以来一直没有受到Googlebot的攻击。<br />
问题的网站位于 www.TheBicyclingGuitarist.net/ 在此之前更新代码时，我从这个
NG和样式表NG获得了很多帮助。
我的主持人'科技人员刚给我发了以下信息。是不是可以指定
UTF-8作为服务器级HTTP标头中的字符集？是否可以
验证XHTML 1.0严格的代码？
**************** ********************************** ***********
如果是IIS的配置错误，那么问题就是为该服务器上托管的每个站点提供
本身
IIS这不是这种情况。我只能在您的网站之间找到两个
的差异，Google没有更新，以及
的网站。
1）你有一个自定义字符集也在
服务器级别的HTTP标题中指定
2）你正在使用严格的XHTML。
我很好奇为什么你选择XHTML严格而不是传统？这是来自broadbandreports.com的
引用，其中包含完整的链接
http://www.broadbandreports.com/faq/...ebmonks?text=1
"如果您使用的是XHTML，您应该努力使您的页面验证为
XHTML 1.0 Transitional。对于现实世界的网站来说，XHTML 1.0 Strict标准有点过于局限了。
我的建议仍然是你和谷歌交谈找出来为什么他们的机器人
都得到了406错误，为什么它没有更新内容它不是
得到错误。如果您愿意，我很乐意将HTTP
标头重置为默认设置，以便您的网站与此服务器上托管的所有其他
网站完全匹配。
-----原帖-----
来自：Chris Watson
收件人：XXXXXXXXXXXXX
发送时间：2004年10月26日星期二下午5:16
主题：RE：Jesse，你真的需要看到这个。
我发布了来自您最近两封电子邮件的信息，一封邮件在
搜索引擎新闻组中。这家伙的答案怎么样？这很简短，而且很可爱。
骑自行车的吉他手写道：
My web site has not been spidered by Googlebot since April 2003. The site in
question is at www.TheBicyclingGuitarist.net/ I received much help from this
NG and the stylesheets NG when updating the code before then.
My host''s tech guy just sent me the following. Isn''t it okay to specify
UTF-8 as the charset in the HTTP headers at the server level? Isn''t it okay
to have validated XHTML 1.0 strict code?
************************************************** ***********
If it was an misconfiguration with IIS the problem would be presenting
itself for every site that is hosted on that server under that instance of
IIS which isn''t the case here. I have only been able to find two
differences between your site which Google isn''t updated, and the sites that
are.
1) You have a custom charset also specified in the HTTP headers at the
server level
2) You are using XHTML strict.
I am curious why you chose XHTML strict rather than traditional? Here''s a
quote from broadbandreports.com with the full link at
http://www.broadbandreports.com/faq/...ebmonks?text=1
"If you are using XHTML you should strive to make your pages validate as
XHTML 1.0 Transitional. The XHTML 1.0 Strict standard is a bit too confining
for real world web sites."
My suggestion is still that you talk to Google to find out why their bot
both is getting a 406 error, and why it isn''t updating the content it isn''t
getting an error on. If you would like I would be happy to reset the HTTP
headers to the default setting so your site identically matches every other
site hosted on this server as far as IIS goes.
----- Original Message -----
From: Chris Watson
To: XXXXXXXXXXXXX
Sent: Tuesday, October 26, 2004 5:16 PM
Subject: RE: Jesse, you really need to see this.
I posted the information from your last two emails in one message at a
search engines newsgroup. What about this guy''s answer? It''s short and
sweet.
The Bicycling Guitarist wrote:
以下是来自科技人员的两条消息在我的主持人关于我的Googlebot问题，反之亦然。
The following are two messages from the tech guy at my host concerning my
problems with Googlebot or vice versa.
问题似乎与您的IIS配置有关。谷歌发送
接受：text / html，text / plain;这当然对于一个
机器人来说很有意义，因为它不需要任何其他东西。你的IIS似乎是错误地配置为发送406不可接受的消息，当它看到
时这个。
如果你接受text / *你得到你的页面。它似乎与
charset无关。
The problem seems to be with your IIS configuration. Google sends
Accept: text/html,text/plain; which of course makes good sense for a
robot as it doesn''t want anything else. Your IIS appears to be
incorrectly configured to send a 406 not acceptable message when it sees
this.
If you accept text/* you get your page. It doesn''t seem to be linked to
the charset.
推荐答案
2004年10月28日星期四06： 26:27 GMT，骑自行车的吉他手
< Ch *** @ TheBicyclingGuitarist.net>写道：
On Thu, 28 Oct 2004 06:26:27 GMT, The Bicycling Guitarist
<Ch***@TheBicyclingGuitarist.net> wrote:
我的网站自2003年4月以来一直没有被Googlebot抓住。
问题的网站位于 www.TheBicyclingGuitarist.net/ 我在
NG和样式表NG中获得了很多帮助之前的代码。
我主持人的技术人员刚给我发了以下信息。是不是可以指定
UTF-8作为服务器级HTTP标头中的字符集？难道
好吗
验证XHTML 1.0严格代码？
My web site has not been spidered by Googlebot since April 2003. The
site in
question is at www.TheBicyclingGuitarist.net/ I received much help from
this
NG and the stylesheets NG when updating the code before then.
My host''s tech guy just sent me the following. Isn''t it okay to specify
UTF-8 as the charset in the HTTP headers at the server level? Isn''t it
okay
to have validated XHTML 1.0 strict code?
我在alt.html中回复 - 是的，UTF-8和XHTML（作为text / html）在PR4上放了
我的网站，并且我的关键字位于顶部。问题必须在其他地方使用
。
I replied in alt.html - yep, UTF-8 and XHTML (served as text/html) has put
my site at PR4 and is on top for my keywords. The problem must lie
elsewhere.
2004年10月28日星期四，自行车吉他手写道：
On Thu, 28 Oct 2004, The Bicycling Guitarist wrote:
我的网站自2003年4月以来一直没有被Googlebot抓住。
我主持人的技术人员刚给我发了以下信息。是不是可以指定
UTF-8作为服务器级HTTP标头中的字符集？
肯定是。
< http://google.com/search?q = www.unics.uni-hannover.de / nhtcapri / multilingual1.html>
是否可以验证XHTML 1.0严格的代码？
我认为没关系。但是你为什么要编写XHTML 1.0而不是HTML 4.01？
有什么好的理由还是只是kewl？
2）你正在使用严格的XHTML。
我很好奇为什么你选择严格的XHTML而不是传统的？
如果你使用XHTML，你应该努力让你的页面验证为XHTML 1.0 Transitional。对于真实世界的网站来说，XHTML 1.0 Strict标准有点过于局限。
My web site has not been spidered by Googlebot since April 2003.
My host''s tech guy just sent me the following. Isn''t it okay to specify
UTF-8 as the charset in the HTTP headers at the server level?
It certainly is.
<http://google.com/search?q=www.unics.uni-hannover.de/nhtcapri/multilingual1.html>
Isn''t it okay
to have validated XHTML 1.0 strict code?
I think it''s okay. But why are you writing XHTML 1.0 instead of HTML 4.01?
Is there any good reason or is it just "kewl"?
2) You are using XHTML strict.
I am curious why you chose XHTML strict rather than traditional?
"If you are using XHTML you should strive to make your pages validate as
XHTML 1.0 Transitional. The XHTML 1.0 Strict standard is a bit too confining
for real world web sites."
这是荒谬的，因为任何验证为[X]的文档HTML严格也
验证为[X] HTML Transitional。这个人是无能为力的。
我没有迹象表明谷歌正在与XHTML斗争 - 但是你有什么理由来编写XHTML 1.0而不是HTML 4.01严格？
-
热门发布。
Usenet上最令人恼火的事情是什么？
This is absurd because any document that validates as [X]HTML Strict also
validates as [X]HTML Transitional. This person is clueless.
I have no indication that Google struggles with XHTML - but what''s your
reason to write XHTML 1.0 rather than HTML 4.01 Strict?
--
Top-posting.
What''s the most irritating thing on Usenet?
" Andreas Prilop" < NH ****** @ rrzn-user.uni-hannover.de>在消息中写道
新闻：Pine.GSO.4.44.0410281439180.12878-100000@s5b003 ...
"Andreas Prilop" <nh******@rrzn-user.uni-hannover.de> wrote in message
news:Pine.GSO.4.44.0410281439180.12878-100000@s5b003...
2004年10月28日星期四，The Bicycling Guitarist写道：
On Thu, 28 Oct 2004, The Bicycling Guitarist wrote:
我的网站自2003年4月以来一直没有被Googlebot抓住。
我主持人的技术人员刚给我发了以下信息。不是吗>> 2）你是严格使用XHTML。
我很好奇为什么你选择严格的XHTML而不是传统的？
如果你使用的是XHTML，你应该努力制作你的页面验证为XHTML 1.0 Transitional。对于真实世界的网站来说，XHTML 1.0 Strict标准有点过于局限。
这很荒谬，因为任何验证为[X] HTML Strict的文档也会验证
as [X] HTML Transitional。这个人是无能为力的。
My web site has not been spidered by Googlebot since April 2003.
My host''s tech guy just sent me the following. Isn''t it >> 2) You are
using XHTML strict.
I am curious why you chose XHTML strict rather than traditional?
"If you are using XHTML you should strive to make your pages validate as
XHTML 1.0 Transitional. The XHTML 1.0 Strict standard is a bit too
confining
for real world web sites."
This is absurd because any document that validates as [X]HTML Strict also
validates as [X]HTML Transitional. This person is clueless.
我会向他指出这一点。
我没有迹象表明谷歌正在与XHTML斗争 - 但是什么'你写XHTML 1.0而不是HTML 4.01 Strict的理由是什么？
I will point this out to him.
I have no indication that Google struggles with XHTML - but what''s your
reason to write XHTML 1.0 rather than HTML 4.01 Strict?
For Duty and Humanity！我希望在我们开发的时候让不同的
用户代理可以使用我的页面，并且在
的未来更容易转换为xml。
如果技术真的很无能为力，那么即使他认为他有，也许他没有正确配置服务器
。这可以由其他人测试比他更好吗？
Chris Watson
www.TheBicyclingGuitarist.net/
..
For Duty and Humanity! I wish to make my pages more available to different
user-agents as they develop, and to make it easier to convert to xml in the
future.
If the tech really is clueless, then perhaps he hasn''t configured the server
correctly even if he thinks he has. Can this be tested by somebody other
than him?
Chris Watson
www.TheBicyclingGuitarist.net/
..
这篇关于utf-8和xhtml 1.0严格的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
