Hi Simon, > From: "Simon Holywell" <[email protected]> > Subject: Re: [Agavi-Users] Question on POST data redirection after > authentication > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=UTF-8 > > You could put the contents into a db table with a pending flag and then just > pass the row id and a secret/hash (to stop people changing the id) via get. > > You could have another table in which you save the row and then as above but > copy the row from one table to the other once authenticated. > > Another option would be to use a temp file which would be similar to storing > it in a session anyway. > > You could also stick the record into memcached or apc and access it as above.
Interesting ideas and ones I hadn't considered. I specifically like the 'temporary table/pass row ID and secret' one. Let me try that out. > Doesn't your login mechanism use sessions anyway? It does. Good point, that didn't occur to me earlier :) > I am not sure how you would do the reposting though. Yup, that was where I was held up too. I was thinking of generating a new HTTP request with the POST data, but handling the response is a little tricky. Any other suggestions for optimal ways to solve this from others on the list? Vikram _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
