Closed Bug 243534 Opened 20 years ago Closed 12 years ago

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

Categories

(Toolkit :: Places, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: jesse.houwing, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [SmBugEvent])

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
Blocks: 288462
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]
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
Closed: 12 years ago
Resolution: --- → INVALID
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.