Come to think of it, not sure why I'm thinking it has to get passed as POST data: the redirect isn't triggering a second request, right? I just want to pass data from the action to the view. (Though I'm still curious how to POST data in the response.)
I also realized I can manually set response.view and then put my data in the return dict. This works, but I don't like how I have to embed the name of the view instead of the action. Logically this is a redirect from one action to another, so I'd like to do my redirects consistently by specifying the action name 'error' rather than its view name 'default/error.html'. Also, in other cases I would want the other action handler to execute rather than bypass it and use just its view. I guess I could stuff the data into the request or response before calling the action directly. Still seems a bit odd. So I guess my question is: I want some way to redirect to another action in the app and pass it data, but I don't want to pass it as URL vars/args. On Apr 5, 12:38 am, Brian Will <[email protected]> wrote: > I assumed there would simply be a Storage in the response object I > could just stuff things into, but it seems not. So my question is > what's the easiest way to append POST data to a response (for both > cases: a redirect and a non-redirect)? > > Maybe I'm going about this the wrong way. I have a simple 'bad > request' error page which I'd like to redirect to when the URL is no > good, e.g. a bad id passed as an arg. I'd like to pass a message to > this error page, e.g. 'No such post.', but I'd rather that text not > show up in the URL, so I'd like to pass it as POST data.
