CGI.pm sticky hidden fields: why?
From: wana (ioneabu_at_yahoo.com)
Date: 09/29/04
- Next message: Vibhu: "Re: How to embed javascript functionality into a Perl CGI script?"
- Previous message: Sisyphus: "Re: gtk2 / glade problem."
- Next in thread: Bernie Cosell: "Re: CGI.pm sticky hidden fields: why?"
- Reply: Bernie Cosell: "Re: CGI.pm sticky hidden fields: why?"
- Reply: Randal L. Schwartz: "Re: CGI.pm sticky hidden fields: why?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 28 Sep 2004 20:20:22 -0700
Is there any justification for the 'stickiness' of hidden fields? A
web page viewer cannot legitimately enter a value into a hidden field,
so why would anyone want to hold over a value to the next page?
I really got stuck on this one for a while because I was creating a
session and passing the session id in a hidden field and it was
getting stuck there and not changing when it was supposed to until I
added -override=>1.
Also, in passing session id via url, Konqueror seems to have a problem
with this. Even with sample code from the Perl and MySQL book, I had
to go to the address bar and press enter each time as if I was typing
in the address with session id each time for it to work. I did not
bother to test this with Netscape since I prefer passing by hidden
field and that seems to work now that I know they are sticky.
- Next message: Vibhu: "Re: How to embed javascript functionality into a Perl CGI script?"
- Previous message: Sisyphus: "Re: gtk2 / glade problem."
- Next in thread: Bernie Cosell: "Re: CGI.pm sticky hidden fields: why?"
- Reply: Bernie Cosell: "Re: CGI.pm sticky hidden fields: why?"
- Reply: Randal L. Schwartz: "Re: CGI.pm sticky hidden fields: why?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|