Volkan YAZICI wrote:

> 1. How do you cope with "No input file specified." errors. Which way
> you'd suggest to fix this.

  This is the reply of the server:

====
HTTP/1.0 404 Not Found
Connection: Close
Date: Wed, 13 Jul 2005 15:08:30 GMT
Server: Cherokee/0.4.25b02 (UNIX)
Status: 404
Content-type: text/html
X-Powered-By: PHP/4.3.10

No input file specified.
====

  It replies with a 404 error code and includes the PHP error
  message.

  While replying this mail, I have realized it would be integrating to
  integrate it with the rest of the server behavior.  I mean, if PHP
  replies with a 404 error, it should be treated like any other 404;
  hence apply the error handlers.

> (A CGI wrapper for SCRIPT_FILENAME env.  variable? If so, any
> examples?) Also, is it possible to cope with this error by
> intervening cherokee internals? (Like adjusting it automatically
> from cherokee side.) Because, it's going to be very ugly to set
> SCRIPT_FILENAME in every PHP file you have.

  If the PHP engine were fully integrated with the rest of the server
  you wouldn't need any of that, am I wrong?

  I'm going to try to sort this issue out for the 0.4.25 release.

> 2. What should I do to make PHP work in a chroot'ed env.?
> [Hard]Linking PHP binaries inside DocumentRoot?

  The chroot and the document root don't have to be the same if you
  don't want to, so you can do something like this:

  /var/www         - Chroot
  /var/www/bin
  /var/www/lib
  /var/www/htdocs  - DocumentRoot

  Remember that the paths in the configuration must be relative to the
  chroot one.

--
Greetings, alo.
_______________________________________________
Cherokee mailing list
[email protected]
http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee

Reply via email to