#567: GET works, POST doesn't
----------------------------------+-----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: anonymous
Type: defect | Status: new
Priority: low | Milestone:
Component: CherryPy | Version: 0.8
Severity: minor | Resolution:
Keywords: |
----------------------------------+-----------------------------------------
Comment (by [EMAIL PROTECTED]):
{{{
#!html
<blockquote>Perhaps the handler for POST /foo would be best served by
maintaining the state and forwarding that to POST /foo/ . Is there a
reason that this would be undesireable?</blockquote>
}}}
That's not as easy for POST as it is for GET, at least not when using HTTP
redirects (302, 303). The current 'solution' is suboptimal because browser
support for the spec is suboptimal and fragmented. See
http://ppewww.ph.gla.ac.uk/~flavell/www/post-redirect.html. As with #871,
this ticket should probably be set for the "when Hell freezes over"
milestone. ;)
!CherryPy 3 allows the developer to completely stop using buggy redirects
for trailing-slash issues, and just pass control to the proper handler.
Just set {{{tools.trailing_slash.on = False}}}. If you'd like to see this
feature backported to CherryPy 2.2, please open a ticket at
http://www.cherrypy.org.
--
Ticket URL: <http://trac.turbogears.org/turbogears/ticket/567>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears Tickets" 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/turbogears-tickets
-~----------~----~----~----~------~----~------~--~---
