XML Parsing Error in Iceweasel (ampersand in google search results)

Bug #1587067 reported by Peter Fales
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Raspbian
New
Undecided
Unassigned

Bug Description

I'm not sure if this is a bug with Google, with Raspbian, with Firefox, with Iceweasel, or something else. But I can only reproduce it with Iceweasel (38.8.0) on Raspbian (both Jessie and Wheezy). I don't see it with Firefox on other platforms, or with other browsers (like Chromium) on Raspbian.

Specifically, when I do a google search for "Naperville Pet Sitting" I consistently get:

XML Parsing Error: not well-formed Location: http://www.google.com/search?hl=en&ie=UTF-8&q=naperville+pet+sitting Line Number 2, Column 4676:

When I looked at the dumped XML string, around column 4676, I see:

Dog+Patch+Pet+%26+Feed+Naperville,+IL&amp;ludocid=10660246100511880083">Dog Patch Pet & Feed</a>
-------------------------------------------------------------------------------------^^^

Apparently, the browser has problems with the Ampersand at column 4676

Tags: jessie wheezy
Revision history for this message
Peter Fales (9-launchpad-net-fales-lorenz-net) wrote :

For what it's worth, I used VirtualBox to create an x86 installation of Debian Jessie, and while it also uses Iceweasel 38.8.0, it does NOT show this problem. It looks like this problem is specific to Raspbian (or something specific to my installation??)

Revision history for this message
Peter Fales (9-launchpad-net-fales-lorenz-net) wrote :

A few more details. More testing has revealed that the problem only shows up on Raspberry Pi Model 2 and Model 3. The page is rendered correctly on first generation Raspberry Pi and on a Pi Zero.

More digging shows that it's related to the user-agent string from the browser. When the string is

  User-Agent: Mozilla/5.0 (X11; Linux armv7l; rv:38.0) Gecko/20100101 Firefox/38.0 Iceweasel/38.8.0

Google returns

  Content-Type: application/xhtml+xml; charset=UTF-8

which results in the error. When the string is

  Content-Type: text/html

In fact when I use User Agent Switcher to change the string from "armv7l" to "armv6l" the page is correctly rendered on the new hardware!

Pander (pander)
tags: added: jessie wheezy
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.