Re: ssi and Perl/CGI
- From: perrin@xxxxxxxxxxxx (Chad Perrin)
- Date: Sun, 14 May 2006 17:00:08 -0600
On Sun, May 14, 2006 at 06:43:13PM -0400, Ricky Zhou wrote:
First, some tips for looking into further such problems:
* Check the error log-- the messages are usually pretty descriptive.
Unfortunately, I don't have access to the logs. As I mentioned in the
original email, it's a cheapo webhosting account without any shell
access. I can transfer files to and from what amounts to a home
directory for the account, which has a public_ftp directory and a
public_html directory and no logs (which I tend to guess would be in
/var anyway).
* Apache (which I'm assuming that you're using) has great
documentation (http://httpd.apache.org/docs/2.0/howto/ssi.html , for
example).
Thanks for the URL. I'll be going through that page with a fine-toothed
comb, now that I'm using (fighting with) SSI.
For your specific problem, try using <!--#include
virtual="/cgi-bin/bar.pl" -->
How do I go about passing variables to the script via include virtual
without using cookies, then? My understanding is that include virtual
won't allow passing variables via the URL (for example).
(For exec, it's exec cmd, not exec cgi).
I'll give cmd a whirl, though cgi seems to work great if all my page
content is coming from the CGI script. Is there some specific
difference in behavior between cmd and cgi in this of which I'm not
aware?
--
Chad Perrin [ CCD CopyWrite | http://ccd.apotheon.org ]
"There comes a time in the history of any project when it becomes necessary
to shoot the engineers and begin production." - MacUser, November 1990
.
- Follow-Ups:
- Re: ssi and Perl/CGI
- From: Chad Perrin
- Re: ssi and Perl/CGI
- References:
- ssi and Perl/CGI
- From: Chad Perrin
- Re: ssi and Perl/CGI
- From: Ricky Zhou
- ssi and Perl/CGI
- Prev by Date: Re: ssi and Perl/CGI
- Next by Date: Re: ssi and Perl/CGI
- Previous by thread: Re: ssi and Perl/CGI
- Next by thread: Re: ssi and Perl/CGI
- Index(es):
Relevant Pages
|
Loading