Alexandre Jousset wrote:
I respond to myself to clarify some things...
I patched the C::A::Dispatch handler function to print the $path_info variable (got with $r->path_info()) to a file in /tmp. Apparently for the URL localhost/lunae/home/mode3, $path_info is set to '/mode3' instead of '/home/mode3'. So the handler tries to load the module Lunae::Iface::Mode3 instead of Lunae::Iface::Home with run_mode set to 'mode3', and it fails and return a 404 not found message. I don't know why...
Another thing you might look at is to see if you have any other locations that start off with '/lunae' since this might also influence the PATH_INFO even if it doesn't process the response.
Sorry to keep responding to myself, but here is another idea. From the Eagle book:
"The division between the filename and the path informatin depends only on what directories are present".
So do you have a 'home' directory in your document root. This would affect the uri => path_info translation, but not which response handler actually serves the request. Does that make sense?
-- Michael Peters Developer Plus Three, LP
--------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/cgiapp@lists.erlbaum.net/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]