589584 - massport.com - Serves invalid XML unless "Firefox" is present in UA string

Status: RESOLVED WORKSFORME

(Web Compatibility :: Desktop, defect, major)

Description

[qowieury]

User-Agent:       Mozilla/5.0 (Windows NT 6.1; rv:2.0b5pre) Gecko/20100821 Minefield/4.0b5pre
Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0b5pre) Gecko/20100821 Minefield/4.0b5pre

The logan airport page http://www.massport.com/logan-airport/Pages/Default.aspx  does not load on mozilla.  it tries to load but ends when the "pie" is almost full and never gets farther.  the page loads quickly in chrome.

Reproducible: Always

Steps to Reproduce:
1.go to http://www.massport.com/logan-airport/Pages/Default.aspx
2. wait
3.
Actual Results:  
no webpage

Expected Results:  
a loaded webpage

Comment 1

[Matthias Versen [:Matti]]

wfm with SM trunk on win32.
Reporter:
Please try http://support.mozilla.com/en-US/kb/Safe+Mode and if that doesn't help try it with a new profile http://support.mozilla.com/en-US/kb/Managing+profiles

Comment 2

[qowieury]

eventually the site stopped loading (15+ min) and gave this error:

XML Parsing Error: not well-formed
Location: http://www.massport.com/logan-airport/Pages/Default.aspx
Line Number 642, Column 275:											<div class="includeOnContainer"><div class="includeOnHeader"><span>Calling All Explorers!</span></div><div class="includeOnItem includeOnItemsCount4 Features"><div class="fieldType HTML"><div style="text-align:left"><a href="http://www.bostonloganconnect.com" id=www.bostonloganconnect.com title=www.bostonloganconnect.com target="_blank"><img alt="" src="/logan-airport/PublishingImages/Sata200x140.jpg"></a><br />
----------------------------------------------------------------------------------------

Comment 3

[Boris Zbarsky [:bzbarsky, bz on IRC]]

For me the page loads quickly... and gives the XML parse error.  Which is a page bug: it's sending not-well-formed XHTML as application/xhtml+xml.  If I replace "Minefield" with "Firefox" in the UA string (but change nothing else) then the site sends the same data as text/html, which works fine, of course.

I recommend contacting the site and complaining about their broken output (and equally broken browser-sniffing).

Comment 4

[Matthias Versen [:Matti]]

that explains it, i had still Firefox in my UA from a similar google bug testing :-(

Comment 5

[Karl Dubost💡 :karlcow]

No issue with SeaMonkey.