[ This bug is one of the recommendations in the W3C's "Common User Agent Problems" document, URL above. One bug has been filed on each recommendation, for deciding whether we do it and, if not, whether we should. ] 1.10 Allow the user to keep track of completed HTTP POST requests. Users may wish to track and archive HTTP POST requests for the same reasons they wish to track and archive email. For instance, if the user places a book order through a form, and that form uses a POST request, the user should be able to store information about that transaction.
Summary: W3C CUAP: → W3C CUAP: Keep track of completed HTTP POSTs
Need 20843, I would have thought. Gerv
I think it would be enough to: 1. allow form-post results to be saved normally (file->save as). 2. warn when attempting to bookmark form-post results.
This would be hard to do (although I would like it). It would be silly to track *each* POST, since it is used by some search engines and at other places you hardly want to track. We could add a context menu entry "track this request" to form submit buttons. But what about submits via JS? Should there be a dialog which asks whether to track this POST (possibly with the option "never ask again for this page/site")? If we track a POST, we should save (1) the originating page, (2) the post data, (3) the resulting page (1 & 3 best as MHTML with all images). There would be a need for an advanced UI to access the collected data. This would be a nice feature, but it needs further discussion and it is far beyond 1.0.
IMHO this depends more on bug 40867 than on bug 20843, because if I understand it correctly, bug 20843 is about cacheing the data sent to the server in the POST request while bug 40867 is about cacheing the result of the request. Adding dependency.
Depends on: 40867
mass move, v2. qa to me.
QA Contact: tever → benc
moving neeti's futured bugs for triaging.
Assignee: neeti → new-network-bugs
-> http, w/ defaults
Assignee: general → nobody
QA Contact: tever → networking.http
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.