> "John" == John Brooking <[EMAIL PROTECTED]> writes:
>> You take the source, modify the value of hidden fields, and then hit
>> enter when your browser points to c:/local/path/file.html
John> [JOHN] Oh... I never thought of doing that. Thanks for the
John> education!
You've no
> -Original Message-
> From: Etienne Marcotte [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 12, 2001 10:53 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Passing arrays across forms
>
>
> You take the source,
me, too!)
>
> - John
>
> > -Original Message-
> > From: Etienne Marcotte [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, December 12, 2001 10:12 AM
> > To: [EMAIL PROTECTED]
> > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> > Subject: Re: Passing a
rcotte [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 12, 2001 10:12 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Passing arrays across forms
>
>
> Passing them in hidden fields lets user change them at will.
> It's ok if
Passing them in hidden fields lets user change them at will.
It's ok if you are doing all your validity checks at the end of all
forms, but if you're doing them after each section you need to keep
those variables unaccessible to the user, or re-check them at the end.
You do a imple validity check
Sharat,
I tend to prefer hidden form variables to pass data, as cookies could be
unsupported or turned off by the client browser. The CGI.pm module provides
an easy way to access form variables from your Perl script. The O'Reilly
book _CGI Programming with Perl_ has several chapters dedicated
