[cgiapp] Problem recognizing modes in URLs

2005-01-28 Thread Alexandre Jousset
Hello, I'm new to the list, to C::A too and I use C::A::Dispatch. My problem is the following : When I get the page localhost/lunae or localhost/lunae/home, no pb, it says It works ! 2. But when I try to get the page localhost/lunae/home/mode1 (or mode2 or mode3 or

Re: [cgiapp] Problem recognizing modes in URLs

2005-01-28 Thread Alexandre Jousset
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

Re: [cgiapp] Problem recognizing modes in URLs

2005-01-28 Thread Michael Peters
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

Re: [cgiapp] Problem recognizing modes in URLs

2005-01-28 Thread Michael Peters
Michael Peters wrote: Just some ideas. Maybe there's something better than PATH_INFO that Dispatch can use. Any ideas? It might be as simple as stripping the Location off of the beginning of the path and using that. It was my understanding that that's what PATH_INFO was, but maybe not. --

Re: [cgiapp] Problem recognizing modes in URLs

2005-01-28 Thread Michael Peters
Michael Peters wrote: 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

Re: [cgiapp] Problem recognizing modes in URLs

2005-01-28 Thread Alexandre Jousset
Michael Peters wrote: 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:

Re: [cgiapp] Problem recognizing modes in URLs

2005-01-28 Thread Michael Peters
Alexandre Jousset wrote: Michael Peters wrote: I checked and I have neither 'home' in document root nor locations that starts with /lunae. I tried to change Home.pm with Test.pm and getting /lunae/test/mode1 also give me a $path_info of /mode3... :-( Maybe you could bring this up on the

Re: [cgiapp] Problem recognizing modes in URLs

2005-01-28 Thread Alexandre Jousset
Michael Peters wrote: Maybe you could bring this up on the mod_perl list. It seems like a mod_perl problem since C::A::Dispatch is just using the $r-path_info() that mod_perl gives it. I found the cause of the problem... In the document root I had a 'lunae' directory. Deleting it gave me the

[cgiapp] Problem with modes.

2004-11-29 Thread Kasturirangan Rangaswamy
Hi, First up. Sorry for the empty post sent earlier. Need more sleep ;) I am using a series of 4 run modes for a module. Each of the first 3 modes displays an HTML template screen where a user could enter data. In each HTML::Template file, I have a hidden variable like so:

Re: [cgiapp] Problem with modes.

2004-11-29 Thread Michael Peters
Kasturirangan Rangaswamy wrote: Now, I want to add form validation for each of the first 3 mode screens. I propose to do this using CGI::Application::ValidateRM. This would mean introducing 3 'new' run modes for the sake of processing those forms. I am unable to figure out a way where, if