"Tim Lesher" <[EMAIL PROTECTED]> writes: > User agents aren't allowed to automatically fetch a resource with any > method other than HEAD or GET, without user intervention (see RFC > 2616).
They shouldn't, but that's not what happens. Usually using GET wouldn't modify anything and using POST would, but for the latter that isn't all true. > What's the reason you need to "hide" the parameters? Knowing this > might help come up with a solution. I believe URLs are prettier without all the information on it. Using RESTful URLs helps a lot to avoid that as well. I don't know his code, but I have the feeling that he's got a multi-page form and is passing information around. If it is that, he'd be able to use hidden fields (what is very interesting to avoid creating temporary tables on the database or holding a transaction for too long). > For example, it seems as if you really want to raise a CherryPy > InternalRedirect, rather than forcing the browser to accept a 302/303, > retain some state, and take another action. If you do that, then you > can instantiate the exception with a "params" argument, and pass > whatever you need that way. You thought a different thing that I did :-) -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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 -~----------~----~----~----~------~----~------~--~---
