httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Omar Gatto" <>
Subject Re: No Environment Vars in SSI
Date Tue, 09 Jul 2002 06:46:06 GMT
Bingo! Thanks, adding a trailing space resumed parsing of
the page. I also traced the problem to a faulty regular
expression in a IF statement used multiple times. It worked
on my win98 Dev machine, but not on the Linux production
  <!--#if expr="\"$QUERY_STRING\" != /(action=about)/"-->
   href="<!--#echo var="self"-->?action=about"

  <!--#if expr="\"$QUERY_STRING\" != /action\=about/"-->
   href="<!--#echo var="self"-->?action=about"
  <!--#endif -->

Amazing, eh??

- Mike Gatto

----- Original Message -----
From: "Gary Turner" <>
To: <>
Sent: Saturday, July 06, 2002 9:11 PM
Subject: Re: No Environment Vars in SSI

> On Sun, 07 Jul 2002 03:45:56 +0000, omar gatto wrote:
> >Hi!
> >
> >I'm running 1.3.19 on Redhat Linux 7.1. An xSSI script
will not read the
> >$QUERY_STRING variable in an IF statement. However, if I
> >var="last_modified" it will output this var. Httpd docs
say env vars should
> >be prefixed with "$" but this produced an error. Also,
> >produces a string of error messages and halts further
parsing of the page.
> >Plain file includes do work, however. What to do?
> I only tested the printenv include, and it worked fine on
this Debian
> Woody box.  An error possibility occurs to me-- if you
don't use quotes,
> you need to add a space before closing the "comment,"
> <!--#printenv -->
>                 ^ need a space here.
> Without the space, you get:
> [an error occurred while processing this directive].
> --
> gt
> It ain't so much what you don't know that gets you in
> it's what you do know that ain't so.--unk
> ----------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message