Using session occurred to me, but I was put off by the idea of cluttering session with one-time use data. Is it good practice to then remove the data from session after use? Probably doesn't matter, I guess.
On Apr 5, 12:47 am, Arbie Samong <phek...@gmail.com> wrote: > From what I can understand you want your data available even after a > redirect. POST won't have that, so you should either store it on the > session, with cookies or with the database. If it's just temporary I > would suggest using session variables. > > Regards, > Arbie > > On Apr 5, 3:38 pm, Brian Will <brian.thomas.w...@gmail.com> 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.
