On Tue, 2002-10-29 at 02:37, Rimon Barr wrote:
> >> >Anyway, to do this I want to access pages like /View.spy/FrontPage --
> >> >usually PATH_INFO is "/FrontPage" in this case, but it's acting weird for
> >> >me. Just when I thought I had gotten all the kinks out, I'm left with a
> >> >page that simply says "FrontPage not found". So what should I do? If
> >> >necessary I could use /View.spy?FrontPage, but I'd really rather not.
> >> Yeah, that's something out of my control. It's Apache (or another web
> >> server) that's returning that error, because it's trying to find the
> >> entire path, and not stopping at the point of the CGI script. Spyce
> >> doesn't even get called. I'm not sure how to set the permissions to get
> >> this to go away, but it certainly has nothing to do with Spyce. I just
> >> pass on to you what I get from the environment, be it mod_python, CGI,
> >> FCGI, whatever...
> >I'm pretty sure this isn't the case -- I use PATH_INFO like this all the
> >time with CGI scripts. I think the error text is being generated in
> >modules/error.py, coming from a spyce.spyceNotFound exception. I'm not
> >sure where that exception is coming from.
> I see... Then it is a Spyce problem. Well, I can tell you exactly where
> the exception is getting thrown. It's in spyce.py on the 4th line of a
> function called spyceFileCacheGenerate. That filename is coming from
> _spyceCommonHandler lower down in the file. That's a common entry point
> for ALL configurations of Spyce.
> Now, I need to trace it back. Are you in CGI-land (or FCGI, etc...)? If
> you're running via CGI, there are two ways. There's the direct way, and
> the alternative way, if you don't have access to the webserver (see:
> http://spyce.sourceforge.net/doc-conf_source.html). The direct way is to
> declare that .spy files are handled by a cgi-handler in the httpd.conf.
> The alternative method is to put:
> #! /usr/bin/python /home/username/spyce/run_spyceCGI.py
> at the top of your script. Which are you using?
I'm just calling them View.cgi, etc., and putting the #! at the top (for
> Either way, the common entry point is being called from doSpyce() in the
> spyceCGI.py file, but the PATH_TRANSLATED variable is set differently in
> each case. I'll look into it, but some added info about your setup would
PATH_TRANSLATED is usually based on PATH_INFO, so if you're using
PATH_TRANSLATED that might cause problems. SCRIPT_NAME should point to
the right file, I think...?