Hallo, on running some tests with cherokee and a simple SCGI test application, I found a strange behaviour in the SCGI handler and the environment SCRIPT_NAME and PATH_INFO it passes. I set up a rule which redirects any request to the SCGI backend application (match by Incoming IP/Port only). If I use an URL like http://127.0.0.1/index, the /index is put into SCRIPT_NAME by SCGI handler, PATH_INFO remains empty. If I use an URL like http://127.0.0.1/path/index, SCRIPT_NAME is empty while PATH_INFO contains /path/index. I'd expect the REQUEST_URI to be stored into PATH_INFO in both cases (as there is no possibility to specify a script name) and don't see a reason anyway why in first case, SCRIPT_NAME is used while in second case PATH_INFO is used to store the REQUEST_URI (logically, I'd expect cherokee to put /path to SCRIPT_NAME and /index to PATH_INFO).
If this is intended behaviour, I'd be very glad if someone would explain the reason for this to me and the way how I may define which parts of the URL to use as SCRIPT_NAME and which as PATH_INFO. If it's not, it would be nice if it could be fixed. Thanks, Julian _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
