Re: Perl and HTML

As others have already said, you can check with your website's hosting company and see if you can use Server Side Includes (SSI).

There are some other alternatives. You can create an index.cgi to read in your HTML file, swap out some targets for the dynamic information, then spit it out to the web browser. You can also get sophisticated and use a templating module like Template::Toolkit.

Comment on Re: Perl and HTML

Replies are listed 'Best First'.
Re^2: Perl and HTML by Joost (Canon) on Jul 06, 2005 at 20:00 UTC
SSI won't do the trick, because SSI doesn't give you the cookies information. You have to generate the HTML from the CGI script somehow. If there's no dynamic information in the HTML itself do `open HTML,"<","/path to html" or die "Can't open html: $!"; print "Content-type: text/html\n\n",<HTML>; close HTML` [download] At the end of the script. For a more general solution, see HTML::Template (or one of the other template modules) and CGI::Application. Or see Web Applications for a possibly helpful thread. "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply] [d/l]
[OT] SSI and cookies by bmann (Priest) on Jul 06, 2005 at 22:32 UTC
SSI won't do the trick, because SSI doesn't give you the cookies information. Hi Joost, I've seen that statement several times now. Have you looked at `$ENV{HTTP_COOKIE}` in an included cgi? Are you talking about cookies and CGI.pm? If that isn't what you mean, would you explain in a little more detail?	[reply] [d/l]
Re: [OT] SSI and cookies by Joost (Canon) on Jul 06, 2005 at 23:45 UTC
I've tried it. You can't set cookies from an SSI included script. I checked it again, you can read cookies from an SSI included script (in apache httpd at least), but it won't help in this case, because you can't reliably redirect from an SSI included script. "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]
Re^2: [OT] SSI and cookies by bmann (Priest) on Jul 06, 2005 at 23:57 UTC