Edward Z. Yang wrote:
The convention for FastCGI deployment is that you setup some mod_rewrite rules which rewrite:/internal/path to /script.fcgi/internal/path The FastCGI itself sees the second path, and essentially every other FastCGI application knows that it should refer to PATH_INFO (which is equal to /internal/path) not REQUEST_URI (which is /scripts.fcgi/internal/path) for routing.
Why not just give "script.fcgi" a nicer name like "myApp"? You can't use .htaccess to tell Apache which files are FastCGI scripts? Or is the issue that the paths still wind up too long?
_______________________________________________ Ur mailing list [email protected] http://www.impredicative.com/cgi-bin/mailman/listinfo/ur
