Welcome to WebmasterWorld Guest from

Forum Moderators: mack

Message Too Old, No Replies

MSN/Live Search SERPs have a malformed http header

Connection: keep-alive, Transfer-Encoding



5:21 pm on May 2, 2009 (gmt 0)

10+ Year Member

Here are response headers from both search.live.com and search.msn.com. Notice that Connection header has an extrenious "Transfer-Encoding"

HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
X-Powered-By: ASP.NET
P3P: CP="NON UNI COM NAV STA LOC CURa DEVa PSAa PSDa OUR IND", policyref="http://privacy.msn.com/w3c/p3p.xml"
Vary: Accept-Encoding
Content-Encoding: gzip
Date: Sat, 02 May 2009 16:56:37 GMT
Transfer-Encoding: chunked
Connection: keep-alive, Transfer-Encoding
Cache-Control: private

I've noticed this problem today using Firefox browser with Live HTTP headers extension. Earlier i reported bad header issues with msnbot. That header error (typo?) seems not to have been fixed yet. Hey MSNDude what's up with MSN and the http header problems?


5:34 pm on May 2, 2009 (gmt 0)

WebmasterWorld Senior Member jdmorgan is a WebmasterWorld Top Contributor of All Time 10+ Year Member

They've got other HTTP header problems as well. I note that a particular variant of msnbot/1.1 sends an HTTP From: header reading:
From: If-Modified-Since <appropriate date here>

when fetching pages.

Apparently, they don't have much in the way of quality assurance checking at the most fundamental protocol levels. I'm not sure how you can build up a good search engine when the critical infrastructure has bugs... :(



9:49 pm on May 2, 2009 (gmt 0)

10+ Year Member


I've reported the issue via their SERP Feedback link. We'll see if and when they do anything about it.

The reason i noticed it is that this morning search.msn.com servers changed their behavior with respect to Accept-Encoding request header.

[edited by: NemoNemo at 10:00 pm (utc) on May 2, 2009]


5:46 pm on May 5, 2009 (gmt 0)

10+ Year Member


Thanks for reporting this. I'm on it. I'll update you as soon as I have more information!



4:19 pm on May 6, 2009 (gmt 0)

10+ Year Member


We found the cause yesterday and we are working to correct it. Let me know if you continue to have these problems.




Featured Threads

Hot Threads This Week

Hot Threads This Month