434947 - redirect urls appear in location bar autocomplete

Status: RESOLVED WONTFIX

(Firefox :: Address Bar, defect)

Description

[juan becerra [:juanb]]

While testing Fx3rc1 on 10.4.11, if you click on a link whose url you have not typed manually in the location bar, and that redirects you to a different page, you will see the originating url in the location bar autocomplete and the history menu.

According to test 4582 in Litmus, you are not supposed to see the originating url in the location bar autocomplete, nor the history menu.

Steps (using a new profile):
1. Go to https://bugzilla.mozilla.org/attachment.cgi?id=277451
2. Click on the link
3. Go to the location bar and start typing gmail; also check the history menu

Expected: gmail.com should not appear in the location bar nor the history menu

Actual: gmail.com appears

Comment 1

[Kai Liu]

A somewhat related bug is bug 426142, which suggests that all redirects of the 301 permanent variety should not appear, whether typed or not.

Comment 2

[Attila Nagy]

Problem is here, that url-s that are part of a redirect chain will appear in the location bar also.

I've created another testcase, here:
http://safranek.hu/~mrbig/redirect/

This will redirect to b.php what will immediately redirect to c.php. Now if you start typing into the location bar safranek... you'll get the b.php too.

Previous versions only learned the redirect/ and the c.php

In case a site uses redirect urls for authentication or clickthrough logging then those urls can fill up the location bar with useless noise.

Comment 3

[Shawn Wilsher :sdwilsh]

Out of curiosity, how are you doing that redirect (what http status code is being used)?

Comment 4

[Attila Nagy]

302 Found

I use the most common method to redirect in php:

issuing a Header("Location: http://example.org/something");

Comment 7

[Marco Bonardo [:mak]]

redirect sources are currently not shown by default in any history view, but they are shown in the locationbar or any other search ui (like while searching in the sidebar), and I think that's the right behavior cause I may remember part of the source url that is not in the target url, then when searching for that part I would get no results, when actually some result exists instead.
The problem is rather that the source page should be ranked much lower (bug 737836).