Page is expired do you want to re-post message should show info about the original and target page.

RESOLVED INVALID

Status

()

Toolkit
Places
--
enhancement
RESOLVED INVALID
14 years ago
5 years ago

People

(Reporter: Jesse Houwing, Unassigned)

Tracking

(Blocks: 1 bug)

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [SmBugEvent])

(Reporter)

Description

14 years ago
Currently if I choose a page from the history that was generated by a POST
action or hit back when the page has expired results in a messagebox asking me
if I want to repost the values.

It would be nice if mozilla could tell me something about the page the data came
from and the page that is being refreshed.

I was thinking something in the line of:

------------------------------------------------------------------------------
The page you're trying to view has expired and was generated by a POST request.
etc etc...

Originating page:
title: "Search form"
url: http://page uri

Target page:
last title: "Search results"
url" http://page uri

This will give a better idea if it is a good idea to repost the page. 

If the originating page is

title "Customers"
url: http://host/customers.html

and the target page is:

title "Delete action succesful"
url: http://host/deletecustomer.html

                                 [ YES ]   [ NO ]
------------------------------------------------------------------------------


Then I probably don't want to do this again, but there would be no way to know
from the dialog.
Product: Browser → Seamonkey

Comment 1

13 years ago
Note bug 288462.

Updated

13 years ago
Blocks: 288462

Comment 2

12 years ago
The login page is getting expired when ever I try to enter
Tentatively moving to Bookmarks & History
Assignee: general → nobody
Component: General → Bookmarks & History
OS: Windows 2000 → All
QA Contact: general → bookmarks
Hardware: x86 → All
Whiteboard: [SmBugEvent]

Comment 4

7 years ago
I think this is in shared Places code. Moving.
Component: Bookmarks & History → Places
Product: SeaMonkey → Toolkit
QA Contact: bookmarks → places
Places doesn't store history for POST pages (they are filtered at the docshell level)
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INVALID

Comment 6

5 years ago
So the bug should be moved to the docshell then?
You need to log in before you can comment on or make changes to this bug.