9699 - 'back ()' functionality on pages resulting from redirects has incorrect path

Status: VERIFIED FIXED

(Core :: DOM: Core & HTML, defect, P3)

Description

[justin hugh daly]

on cvs build from 12 jul 1999

form on http://server/page_one.html has action http://server/some-path/program
which performs a redirect (via 'location' http header) to
http://server/result.html

a 'back ()' function on this page incorrectly results in
http://server/some-path/page_one.html

i wish i had a url for you, but i'm behind a firewall...

Comment 1

[cbegle]

wrong component

Comment 2

[Mike Shaver (:shaver emeritus)]

This one smells like a necko/history bug to me.  Copying gagan, I have no idea
who owns history.

We can get to Beta1 without this.

Comment 3

[Gagan]

I think radha gets this one. for future reference global history is owned by
waterson and session history by radha.

Comment 4

[Radha on family leave (not reading bugmail)]

After a page is done loading, SH is updated with the new url. In the case of
redirected urls, it will be the new url as passed by necko. So, this s'd be
fixed now. Please verify.

Comment 5

[Prashant Desale]

Actually I'm reopening this bug since I seedifferent results on 4.x and
apprunner.
in 4.x, if I hit back button then intermediate page in this process gets
processed again and third page gets loaded as a result. [Which I think is
correct.]
In above URL there are three pages.
(bug9699_one.html) this is first page you load. Here you click button "Change
Location". This takes you to second page (bug9699_two.html). This second page
redirects you to third page (bug9699_three.html).

In 4.x after coming to third page (bug9699_three.html), if you hit back button,
it takes you to second page (bug9699_two.html), which again redirects you to
third page (bug9699_three.html).

In apprunner after coming to third page (bug9699_three.html), if you hit back
button then it takes you to first page (bug9699_one.html). [This is wrong.
history.back() should take you to second page]

STEPS TO REPRODUCE:
1] Load above URL.
2] Click button "Change Location"
3] Click browser back button.

Comment 6

[leger]

M11 out the door, moving to M12.

Comment 7

[Radha on family leave (not reading bugmail)]

I see how 4.x behaves. But I'm not sure if we want to do that for 5.0. With the
current 4.x behavior, you are stuck with bug9699_three.html. You can never get
back to bug9699_one.html thro' the back button. You have to use the 'Go' menu.
cc'ing don for some help with decision making.  Can people in the cc list
comment please?

Even if we decide to fix this the 4.x way, it can not be done in M12 time frame.
Moving to M14.

Comment 8

[Mike Shaver (:shaver emeritus)]

What if _two.html was dynamic content that didn't always issue a redirect?  We
can't know if we'll get redirected again until we load the page, at which point
we should honour the redirection.

If the page author wants the current (buggy) Mozilla behaviour, he or she can
use history.replace() to remove _two.html's history entry.

Comment 9

[Radha on family leave (not reading bugmail)]

I think I have a patch fix for this. Shall fix for M12.

Comment 10

[Radha on family leave (not reading bugmail)]

I have checked in my patch fix. Marking fixed.

Comment 11

[Prashant Desale]

Verified with 1199-11-29-09.