in reply to Re^2: newb: Best way to protect CGI from non-form invocation?
in thread newb: Best way to protect CGI from non-form invocation?

I would strongly recommend against freely mixing languages (e.g. Perl and PHP) in a single application. If you've already got a Perl application, use it to generate the time stamps and insert them in the output (HTML) that is your form.

Some information that may be of interest in this matter:

<radiant.matrix>
Ramblings and references
The Code that can be seen is not the true Code
I haven't found a problem yet that can't be solved by a well-placed trebuchet
  • Comment on Re^3: newb: Best way to protect CGI from non-form invocation?

Replies are listed 'Best First'.
Re^4: newb: Best way to protect CGI from non-form invocation?
by JCHallgren (Sexton) on Feb 09, 2007 at 03:23 UTC
    At this point, I'm going to have to add some PHP code anyway to site to try and keep (by valid users) certain pages from being viewed in sequence other than I wish. This may possibly have side benefit of helping to block form page from being invoked by invalid users.

    And the only Perl used currently are two (back-end) programs to process the two input forms. The rest of site is just plain HTML (ok, a bit of JavaScript for some cookie handling) for display purposes, so calling it an application is a bit maybe of overkill!