in one of my recent email, I add .to_s to PATH_INFO in camping code. actually, this is probably very wrong. the problem is probably something like PATH_INFO does not exist when using FastCGI. I have not done all my homework, but so far what I found is lighttpd has a special option "broken-scriptfilename": breaks SCRIPT_FILENAME in a wat that PHP can extract PATH_INFO from it (default: disabled) which seems to do what we need. maybe there is an equivalent in Apache, or Camping needs to cut PATH_INFO from SCRIPT_FILENAME. also, I quickly saw a reference about FILEPATH_INFO, I''m not sure what is the difference. or if we can use it. /me back to work..... tanoshimi ne -- gcc -O0 -DRUBY_EXPORT -rdynamic -Wl,-export-dynamic -L. main.o -lruby-static -ldl -lcrypt -lm -o ruby Everyone is trying their hardest to do their job but management has set it up so that it''s impossible. Take the control over your money, track your expenses http://justbudget.com Mathieu -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/camping-list/attachments/20060725/93dfa7c7/attachment.html
apparently FILEPATH_INFO would be the "old" value of PATH_INFO has it was in Apache 1.1 On 7/25/06, Mathieu Jobin <mathieu at justbudget.com> wrote:> > in one of my recent email, I add .to_s to PATH_INFO in camping code. > actually, this is probably very wrong. the problem is probably something > like PATH_INFO does not exist when using FastCGI. > I have not done all my homework, but so far what I found is lighttpd has a > special option > > "broken-scriptfilename": breaks SCRIPT_FILENAME in a wat that PHP can > extract PATH_INFO from it (default: disabled) > which seems to do what we need. maybe there is an equivalent in Apache, or > Camping needs to cut PATH_INFO from SCRIPT_FILENAME. > also, I quickly saw a reference about FILEPATH_INFO, I''m not sure what is > the difference. or if we can use it. > > /me back to work..... tanoshimi ne > > -- > gcc -O0 -DRUBY_EXPORT -rdynamic -Wl,-export-dynamic -L. main.o -lruby-static > -ldl -lcrypt -lm -o ruby > Everyone is trying their hardest to do their job but management has set it > up so that it''s impossible. > Take the control over your money, track your expenses > http://justbudget.com > > Mathieu >-- gcc -O0 -DRUBY_EXPORT -rdynamic -Wl,-export-dynamic -L. main.o -lruby-static -ldl -lcrypt -lm -o ruby Everyone is trying their hardest to do their job but management has set it up so that it''s impossible. Take the control over your money, track your expenses http://justbudget.com Mathieu -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/camping-list/attachments/20060725/4afe1704/attachment.html
may I ask what exactly are you looking for in the PATH_INFO variable ? all the info I can find dates from 1997-2002> grep -i -rn ''PATH_INFO'' . | grep -v "\.svn"./lib/camping.rb:683: k,a=X.D un("/#{e[''PATH_INFO'']}".gsub(/\/+/,''/'')) ./lib/camping/fastcgi.rb:75: #raise [req.env[''SCRIPT_NAME''], req.env[''PATH_INFO''], req.env].inspect ./lib/camping/fastcgi.rb:76: path = req.env[''SCRIPT_NAME''] + req.env[''PATH_INFO''].to_s ./lib/camping/fastcgi.rb:83: req.env[''PATH_INFO''] path.gsub(/^#{dir}/, '''') ./lib/camping-tmp.rb :43:''PATH_INFO'']}".gsub(/\/+/,''/''));k.new(r,e,(m=e[''REQUEST_METHOD'']||"GET")). -tmp is short camping.rb and camping.rb is unabridged. maybe we could find the content of PATH_INFO in some newer variable? Mathieu On 7/25/06, Mathieu Jobin <mathieu at justbudget.com> wrote:> > apparently FILEPATH_INFO would be the "old" value of PATH_INFO has it was > in Apache 1.1 > > > On 7/25/06, Mathieu Jobin < mathieu at justbudget.com> wrote: > > > > in one of my recent email, I add .to_s to PATH_INFO in camping code. > > actually, this is probably very wrong. the problem is probably something > > like PATH_INFO does not exist when using FastCGI. > > I have not done all my homework, but so far what I found is lighttpd has > > a special option > > > > "broken-scriptfilename": breaks SCRIPT_FILENAME in a wat that PHP can > > extract PATH_INFO from it (default: disabled) > > which seems to do what we need. maybe there is an equivalent in Apache, > > or Camping needs to cut PATH_INFO from SCRIPT_FILENAME. > > also, I quickly saw a reference about FILEPATH_INFO, I''m not sure what > > is the difference. or if we can use it. > > > > /me back to work..... tanoshimi ne > > > > -- > > gcc -O0 -DRUBY_EXPORT -rdynamic -Wl,-export-dynamic -L. main.o -lruby-static > > -ldl -lcrypt -lm -o ruby > > Everyone is trying their hardest to do their job but management has set > > it up so that it''s impossible. > > Take the control over your money, track your expenses > > http://justbudget.com > > > > Mathieu > > > > > > -- > gcc -O0 -DRUBY_EXPORT -rdynamic -Wl,-export-dynamic -L. main.o -lruby-static > -ldl -lcrypt -lm -o ruby > Everyone is trying their hardest to do their job but management has set it > up so that it''s impossible. > Take the control over your money, track your expenses > http://justbudget.com > > Mathieu >-- gcc -O0 -DRUBY_EXPORT -rdynamic -Wl,-export-dynamic -L. main.o -lruby-static -ldl -lcrypt -lm -o ruby Everyone is trying their hardest to do their job but management has set it up so that it''s impossible. Take the control over your money, track your expenses http://justbudget.com Mathieu -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/camping-list/attachments/20060725/dee8cbea/attachment-0001.html
On Tue, Jul 25, 2006 at 11:35:27AM +0900, Mathieu Jobin wrote:> may I ask what exactly are you looking for in the PATH_INFO variable ?SCRIPT_NAME contains the path the script is attached to. PATH_INFO is the remaining parts of the URL. For example, under traditional CGI, a blog.rb placed under the web server''s /scripts/ directory could be called like this: REQUEST_URI SCRIPT_NAME PATH_INFO ------------------------+------------------+------------- /scripts/blog.rb/ /scripts/blog.rb / /scripts/blog.rb/add /scripts/blog.rb /add /scripts/blog.rb/view/1 /scripts/blog.rb /view/1 In most cases, we''re mounting the script at /. Or maybe at a directory: /app. Camping is designed to use these same variables. Usually it''s a matter of finding the right configuration settings. I don''t think mod_fastcgi or mod_fcgid have options to mount a single app, though, so it might need some rewrite rules. _why
actually i would not mind using some rewriting rules, mounting the app at a special URL is not mandatory. all I want is to get Camping to work with Apache/mod_fastcgi which does not seems to be possible, as it is now. thanks On 7/25/06, why the lucky stiff <why at whytheluckystiff.net> wrote:> > On Tue, Jul 25, 2006 at 11:35:27AM +0900, Mathieu Jobin wrote: > > may I ask what exactly are you looking for in the PATH_INFO variable ? > > SCRIPT_NAME contains the path the script is attached to. > PATH_INFO is the remaining parts of the URL. > > For example, under traditional CGI, a blog.rb placed under the web > server''s > /scripts/ directory could be called like this: > > REQUEST_URI SCRIPT_NAME PATH_INFO > ------------------------+------------------+------------- > /scripts/blog.rb/ /scripts/blog.rb / > /scripts/blog.rb/add /scripts/blog.rb /add > /scripts/blog.rb/view/1 /scripts/blog.rb /view/1 > > In most cases, we''re mounting the script at /. Or maybe at a directory: > /app. > > Camping is designed to use these same variables. Usually it''s a matter of > finding the right configuration settings. I don''t think mod_fastcgi or > mod_fcgid have options to mount a single app, though, so it might need > some > rewrite rules. > > _why > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list >-- gcc -O0 -DRUBY_EXPORT -rdynamic -Wl,-export-dynamic -L. main.o -lruby-static -ldl -lcrypt -lm -o ruby Everyone is trying their hardest to do their job but management has set it up so that it''s impossible. Take the control over your money, track your expenses http://justbudget.com Mathieu -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/camping-list/attachments/20060725/e126293b/attachment.html