Closed Bug 530786 Opened 11 years ago Closed 6 years ago
.live .com - XML Parsing Error caused by sniffing for "Firefox" instead of "Gecko"
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:22.214.171.124pre) Gecko/20091124 SeaMonkey/2.0.1pre - Build ID: 20091124000514 I confirm the problem. I believe that the problem is not due to an error in SeaMonkey but to a malformed web page. Reporter: please try to contact the site webmaster after reading http://www.mozilla.org/projects/tech-evangelism/site/procedures.html and any relevant pages linked from there; then report here to say if you were successful.
Assignee: nobody → english-us
Status: UNCONFIRMED → NEW
Component: General → English US
Ever confirmed: true
OS: Windows XP → All
Product: SeaMonkey → Tech Evangelism
QA Contact: general → english-us
Hardware: x86 → All
Summary: XML Parsing Error → skydrive.live.com - XML Parsing Error
(In reply to comment #1) > > I confirm the problem. I believe that the problem is not due to an error in > SeaMonkey but to a malformed web page. > The problem exists not on Firefox 3.5.5.
Answer: Build identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:126.96.36.199) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729)
They're probably sniffing -- server-side -- for "Firefox" in the UA string and feeding other browsers broken XML. We've seen several instances of this in TE bugs lately. Try spoofing as Firefox 3.5 (or simply adding "not Firefox 3.5" to a Seamonkey UA string) and see if that fixes it. On Camino, as long as "Firefox/" is present followed by a version number (e.g., 2.0, 3.0, 3.5), the site works great. If I remove that part of the UA string, it immediately breaks. cl
Summary: skydrive.live.com - XML Parsing Error → skydrive.live.com - XML Parsing Error caused by sniffing for "Firefox" instead of "Gecko"
In reply to comment #6 On SeaMonkey 2, setting the UA to Mozilla/5.0 (X11; U; Linux i686; en-US; rv:188.8.131.52pre) Gecko/20091125 SeaMonkey/2.0.1pre, a sibling of Firefox/3.5 by means of the "UserAgent Switcher" extension, makes the problem disappear. Chris, I knew about this kind of "problem sites" but somehow I'd forgot about them. Brilliant! Urs, you can either use UserAgent Switcher (if it's installed) to set your UA string to something mimicking Firefox, or try the following (in SeaMonkey 1.1.18): 1. Type "about:config" (without the quotes) into the URL bar, then hit Enter 2. Type "usera" (without the quotes) in the Filter box 3. If there exists a preference named "general.useragent.extra.seamonkey", then: 3.1. Click right, then New => String 3.2. New name: "general.useragent.extra.firefox" (without quotes) 3.3. New value: "NOT Firefox/3.5.5" (without quotes) 3a. Otherwise: 3a.1. Copy your SeaMonkey 1.1.18 useragent (e.g. from comment #0) to the clipboard 3a.2. If you see "general.useragent.override", click right on it, then "Modify". If you don't see it, create it in a way similar to 3.1 and 3.2 above 3a.3. New value: Paste (Ctrl+V) the clipboard contents, then add " NOT Firefox/3.5.5" (without the quotes) at the end 4. Try browsing your problem site and note whether it works or not. 5. In about:config, click right on the preference created or modified at step 3 or 3a above, then Reset. (This sets your user-agent string back to normal.) I expect that that it will work at step 4 and go back to "not working" after step 5, which would mean that the site is doing "broken browser sniffing".
Chris and Tony, thanks for the tip. I have followed the instructions from you. It's the additional entry "Firefox/3.5 " that's fix the problem. My UA now modified to: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:184.108.40.206) Gecko/20090825 SeaMonkey/1.1.18 NOT Firefox/3.5 Greetings from Switzerland
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
We need to leave this open, since Microsoft clearly hasn't fixed it.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
(In reply to comment #6) > They're probably sniffing -- server-side -- for "Firefox" in the UA string and > feeding other browsers broken XML. We've seen several instances of this in TE > bugs lately. It's also a common Microsoft bug; we've seen it before at live.com subdomains and other Microsoft properties.
Status: REOPENED → NEW
Now redirected to https://onedrive.live.com/about/en-us/ No issue. Site has changed.
Assignee: english-us → nobody
Status: NEW → RESOLVED
Closed: 11 years ago → 6 years ago
Component: English US → Desktop
Resolution: --- → INVALID
Product: Tech Evangelism → Web Compatibility
You need to log in before you can comment on or make changes to this bug.