W3C CUAP: Keep track of completed HTTP POSTs

RESOLVED WONTFIX

Status

()

Core
Networking: HTTP
RESOLVED WONTFIX
18 years ago
3 years ago

People

(Reporter: gerv, Unassigned)

Tracking

Trunk
Future
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(URL)

[ 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
Blocks: 68427
Depends on: 20843
Need 20843, I would have thought.

Gerv

Updated

18 years ago
Hardware: PC → All

Comment 2

18 years ago
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.

Comment 4

18 years ago
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

Updated

18 years ago
Target Milestone: --- → mozilla1.2

Updated

18 years ago
Target Milestone: mozilla1.2 → Future

Comment 5

17 years ago
mass move, v2.
qa to me.
QA Contact: tever → benc

Updated

17 years ago
Depends on: 90722

Comment 6

16 years ago
moving neeti's futured bugs for triaging.
Assignee: neeti → new-network-bugs

Comment 7

16 years ago
-> http, w/ defaults

Updated

16 years ago
Component: Networking → Networking: HTTP
QA Contact: benc → tever
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.