Hi Eric, > http://localhost:8080 page_info doesn't exist > http://localhost:8080/ page_info doesn't exist > http://localhost:8080/foo page_info = foo > > http://hoohoo.ncsa.uiuc.edu/cgi/env.html > > """ The extra path information, as given by the client. In other words, > scripts can be accessed by their virtual pathname, followed by extra > information at the end of this path. The extra information is sent as > PATH_INFO. This information should be decoded by the server if it comes > from a URL before it is passed to the CGI script > """ > > Whether or not this means that there should be a path_info, I believe it > means that if there is, the path remaining includes the '/'. This is > not too big a deal for me because I have worked around it.
I guess I tested it before.. I would bet Apache was working in that way and that was the reason to remove the slash. > Another problem I found is that if the CGI returns a 404 error as > well as its own 404 display, I get the server's 404. Maybe this is > a patchy specific but I was under the impression that the CGI > program had the option of returning its own data in the case of > errors detected. 0.4.29 already supports that behavior: http://alobbs.com/pipermail/cherokee/2005-November/001071.html > I've also noticed a similar problem with 500 errors. Nothing from > standard error is placed into the log. I'm currently debugging a > submit button problem. I get a 500 error message and nothing else > so I am debugging relatively blind. after spending a bit time > looking over the CGI handler, I'm relatively certain that the way > you handle the 404 and 500 error codes are part of the problem. > > not sure exactly how to fix it yet but that's where it lies. The CHEROKEE_TRACE facility from HEAD might help. Anyway, if you provide me more information about what the problem, I will try to trace it back. :) -- Greetings, alo. _______________________________________________ Cherokee mailing list [email protected] http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee
