On Sat, July 14, 2007 1:26 pm, Al wrote: > You guys confirmed my understanding, it can't be done in a reasonable > manner. > > I'm adding a simple CAPTCHA to an existing page and don't want to > bother tracing the code that > modifies the session buffer. It's obvious that the code is resetting > the buffer, so it messes up my > saving of the security number. Obviously, I don't want it exposed > with GET or shown in the HTML > source. > > I'll just make my own simple session-like buffer with a tmpfile() > outside the webspace. I suspect you have a flaw in your basic HTTP interaction logic rather than whatever it is you think is going wrong... I'm not sure what you mean by "session buffer" either... A lot of error_log() statements to see where you are storing/retrieving your security number will probably help you far more than trying to re-invent sessions... -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some indie artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
