Firefox corrupts URLs in Netflix emails

Bug #191426 reported by gbryant
2
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: firefox

I got an email from NetFlix telling me a movie is on the way, and the message contains this tag:
<a href=3D"http://www.netflix.com/MovieDisplay?&amp;movieid=3D70068654&amp;trkid=3D1767">Vitus</a>

When I copy the link location in the visible email (I use Evolution) I get this URL:
http://www.netflix.com/MovieDisplay?&amp;movieid=70068654&amp;trkid=1767

But when I click it and it opens the browser, Firefox winds up with this in the location box:
http://www.netflix.com//Movie?amp;trkid=1767&amp;movieid=70068654

It has added a slash before "Movie" and omitted the "&" between the "?" and "amp;". It's also failed to convert the "&amp;"s to "&"s.

This doesn't work. But if I edit the URL manually to say this:
http://www.netflix.com/Movie?&trkid=1767&movieid=70068654
...it works.

Either Evolution of Firefox is dropping the ball here.

ProblemType: Bug
Architecture: i386
Date: Tue Feb 12 19:49:11 2008
DistroRelease: Ubuntu 7.10
NonfreeKernelModules: nvidia
Package: firefox 2.0.0.12+2nobinonly+2-0ubuntu0.7.10
PackageArchitecture: i386
SourcePackage: firefox
Uname: Linux Karabekian 2.6.22-14-generic #1 SMP Fri Feb 1 04:59:50 UTC 2008 i686 GNU/Linux

Tags: apport-bug
Revision history for this message
gbryant (bryants) wrote :
Revision history for this message
Matthew Tighe (tighem) wrote :

This is probably a parsing error in evolution. I know "&amp" is actually some sort of HTML or Javascript thing. Apparently however (from googling), Netflix shouldn't be putting & in their URLs, either. It's not technically wrong but is not recommended.

Changed in evolution:
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue is known and already fixed in hardy

Changed in evolution:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: Incomplete → Fix Released
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.