#5382: create_update.delete_object always needs a confirmation page
-----------------------------------+----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: nobody
Status: closed | Component: Generic views
Version: SVN | Resolution: wontfix
Keywords: delete_object | Stage: Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-----------------------------------+----------------------------------------
Comment (by [EMAIL PROTECTED]):
Because GET requests should always be safe. Some browsers, extensions,
ISPs, caches, etc can pre-fetch information from links. There was a big
problem a while back when Google introduced their caching mechanisms
client-side, where the extension would end up pre-fetching "delete" links.
"POST" forms are never pre-fetched. See also the HTTP 1.1 Spec, Section 9:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html. (Small quip:
restyle an INPUT to look like a link. You don't need JavaScript!)
--
Ticket URL: <http://code.djangoproject.com/ticket/5382#comment:3>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
