One time, I had to prototype that would be relatively stable, yet worked for WebTV web clients and hyper-secure IE/NS browsers.
WebTV doesn't know what cookies are: all Set-Cookie headers are condemned to /dev/null. Ouch. PHP's session-handling functions and Perl's Apache::Session module are both ruled out by spec.... (I missed CGI::Session in this feasibility study.) IE and NS can be configured not to record cookies at all.
I ended up prototyping a DB-based system that relied on both cookies and IP address/web client pairs. If the cookie was verified to work, the fallback system (IP address/web client pair) was disabled automatically.
Another possibility is to explicitly store an index to the session information as a form/URL variable, in the HTML, whose value's validity expires in a reasonable timeframe. The actual information would be stored in a DB backend (cf. prior posts for examples).
In reply to Re: CGI.pm param not following post
by zaimoni
in thread CGI.pm param not following post
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |