#16623 closed Bug (wontfix)
APPEND_SLASH changes request method
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Core (Other) | Version: | 1.3 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Discovered this while working on some backbone/piston CRUD
if my url is foo/
and I send a DELETE to foo, what actually happens is a GET on foo/ which when using CRUD is problem.
Obviously this is my fault for not correctly matching my urls, but discovering the root cause of why your DELETE is a GET is a surprising amount of effort!
Thanks
Change History (2)
comment:1 by , 13 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:2 by , 13 years ago
Note:
See TracTickets
for help on using tickets.
Leaving this closed, since the ticket opener closed it. For future searchers, the problem here is that the 'foo' url correction to 'foo/' uses a 301 redirect, which sets the Location header. Unfortunately, most user agents simply fall back to GETing at the new location, rather than asking the user if they wish to repeat the request. A 307 might fix the problem in some user agents, but it would confuse others.
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html