Bug 20603 – response header says WAP but it sends XHTML

• Status: RESOLVED
• Resolution: WORKSFORME
• Component: Evangelism

[David Carson]

On the mobile version of the site, when I pick home I see the page source. It seems that it is because they have sent the wrong content type in the http response. 
Here is a cut and paste from WebInspector (ToT mainline). I removed the cookie, and cleaned it up to make it more readable.

URL: 
http://twitter.com/home

Request Headers:-
Accept:application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Referer:http://twitter.com/friends
User-Agent:Mozilla/5.0 (iPhone; U; CPU like Mac OS X; en) AppleWebKit/420.1 (KHTML, like Gecko) Version/3.0 Mobile/4A93 Safari/419.3

Response Headers:-
Cache-Control:no-cache, no-store, must-revalidate, pre-check=0, post-check=0
Connection:close
Content-Length:4045
Content-Type:text/vnd.wap.wml; charset=utf-8
Date:Tue, 02 Sep 2008 18:07:44 GMT
Expires:Tue, 31 Mar 1981 05:00:00 GMT
Last-Modified:Tue, 02 Sep 2008 18:07:44 GMT
Pragma:no-cache
Server:hi
Set-Cookie:lang=; path=/, _twitter_sess=<snipped>; domain=.twitter.com; path=/
Status:500 Internal Server Error

[Robert Blaut]

I'm unable to reproduce the problem. Is it already fixed?

[George Staikos]

That's server error for sure, and reported to be fixed.  I say re-open if it can be reproduced in the future but I think the only answer is to go back to the site operator.