266213 - washingtonpost.com - serving RealMedia (.smi) as text/plain

Status: RESOLVED WORKSFORME

(Tech Evangelism Graveyard :: English US, defect, P2)

Description

[theraven]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10.1

Hi

If you goto the washingtonpost video section, the area reserved for the plugn
produces only an eare containing html. This same window displays fine under IE 6



Reproducible: Always
Steps to Reproduce:
1.go to url http://www.washingtonpost.com/wp-srv/mmedia/liveonline/102204-2v.htm
2.
3.

Actual Results:  
html tags appear in plugin area

Expected Results:  
run the rm movie (works under IE 6)

Comment 1

[Bill Mason]

http://www.washingtonpost.com/wp-srv/mmedia/liveonline/102204-2v.smi

GET /wp-srv/mmedia/liveonline/102204-2v.smi HTTP/1.1
Host: www.washingtonpost.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a5)
Gecko/20041024 Firefox/0.9.1+
Accept:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Referer: http://www.washingtonpost.com/wp-srv/mmedia/liveonline/102204-2v.htm
Cookie: WPATC=A=1:D=3:C=2:C=27:E=JIGIC:S=54:S=245:B=7:B=59:B=72:B=101:VS=3;
WPNIUCID=WPNI1079210829931.1399;
UPROF=WU9CPTE5NjYrRz1tYWxlK1pJUD05ODY4MitVVD1leHBsaWNpdCtDPVVuaXRlZCBTdGF0ZXMrQj1QUk9GRVMrQj1PVEhfUkVTUCtCPUlOVEVSTkVUK0I9U0laRV8y;
sauid=3; UPDATED=1098420919;
DMSEG=D166F24A3BBD6730&F04462&417D9D84&41805876&0&&417E2303&2882060AA0DF927CFFBAABBF85E1C1D3;
wpniuser=[e-mail]
Pragma: no-cache
Cache-Control: no-cache

HTTP/1.x 200 OK
Server: Sun-ONE-Web-Server/6.1
Date: Wed, 27 Oct 2004 02:25:09 GMT
Content-Length: 1355
Content-Type: text/plain
Last-Modified: Fri, 22 Oct 2004 15:04:27 GMT
Etag: "54b-4179217b"
Accept-Ranges: bytes

They're serving the video as text/plain, so we treat it as such.

Not a browser bug.  They need to fix their server setting.
->TE