On 01-mar-09, at 14:24, M. David Peterson wrote: > sue that I keep running into and still seems to be a problem with > this release has to do with the FastCGI module appending the > directory name for a given behavior to the URI passed to the FastCGI > process. I'll leave the example URI that follows up and running for > a few hours to allow time to see the problem I'm referring to: > > http://dev.amp.fm/service/search/return-events-by-location/?location=salt+lake+city&topic=%7C&time_scope=next_7_days&format=atom
The value of the FastCGI variables depend on how the server is configured. For instance, it depends on where the FastCGI handler is being configured (a directory, and extension, etc). There is something quite important at this regard. There are two sort of FastCGI/SCI setups, and you must point Cherokee which one it will handle: - Using real files: The most common case is PHP. Cherokee has to check if the file exists, and in case it does, build the variables according to its path. - Passing all the requests to the application server: In this case, Cherokee does not need to check whether the request matches a file on the disk. Thus, the algorithm for building the variables is slightly different. The "Check File" checkbox (in the FastCGI configuration) points Cherokee the type of setup. If there is something wrong with the paths passed to the FastCGI, it might be because of this. Could you please check whether the option is set correctly? -- Greetings, alo http://www.alobbs.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
