Re: Troubleshooting: Camping 2.0 on CGI on a shared host

2008-07-14 Thread Magnus Holm
What about dropping the idea of config.ru and just create a dispatch.cgi like this? #!/usr/bin/env ruby require 'app' Rack::Handler::CGI.run(App) On Fri, Jul 11, 2008 at 7:33 AM, Eric Mill [EMAIL PROTECTED] wrote: Some progress: I put most of the code from dispatch.cgi into a

Re: Troubleshooting: Camping 2.0 on CGI on a shared host

2008-07-14 Thread Eric Mill
Actually, that is what I'm doing now, and I'm still seeing the same behavior -- redirects preface the URL with /dispatch.cgi/, and the Camping cookies are valid under path /dispatch.cgi/. I have another camping app on the same account, that uses Camping 1.5.180, and when I first tried it under

Re: Troubleshooting: Camping 2.0 on CGI on a shared host

2008-07-14 Thread Bluebie, Jenna
Could you show us the .htaccess please? :) ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list

Re: Troubleshooting: Camping 2.0 on CGI on a shared host

2008-07-14 Thread Bluebie, Jenna
Also, is it possible that you could simply rename dispatch.cgi to something like 'appname' and use htaccess to grant that file cgi execution type permissions? Or does this need to be on the root of a domain? ___ Camping-list mailing list

Re: Troubleshooting: Camping 2.0 on CGI on a shared host

2008-07-14 Thread Bluebie, Jenna
can you please try adding to htaccess SetEnv SCRIPT_NAME /path/to/app Assuming your dispatch is in /path/to/app/dispatch.cgi Let us know what happens! ___ Camping-list mailing list Camping-list@rubyforge.org

Re: Troubleshooting: Camping 2.0 on CGI on a shared host

2008-07-14 Thread Bluebie, Jenna
No wait, this is even better, at the end of your RewriteRule, put: [env=SCRIPT_NAME:/path/to/app] Let us know what happens! ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list

Re: Troubleshooting: Camping 2.0 on CGI on a shared host

2008-07-14 Thread Eric Mill
I'm not able to get this working, I can't seem to affect the environment, either using the SetEnv approach, or by including that at the end of RewriteRule. How does Camping use the env in forming its understanding of its base URI? Forming URLs using the R method does not pre-pend /dispatch.cgi/,

Re: Troubleshooting: Camping 2.0 on CGI on a shared host

2008-07-14 Thread Bluebie, Jenna
I really do think we should build in the SCRIPT_URL || SCRIPT_NAME thingo. This is going to be a relatively common situation. Totally worth the bytes. ___ Camping-list mailing list Camping-list@rubyforge.org

Re: Troubleshooting: Camping 2.0 on CGI on a shared host

2008-07-14 Thread Julik Tarkhanov
On Jul 15, 2008, at 12:58 AM, Bluebie, Jenna wrote: I really do think we should build in the SCRIPT_URL || SCRIPT_NAME thingo. This is going to be a relatively common situation. Totally worth the bytes. You might, but this is a can of worms. See, right now for example, if you need to

Re: Troubleshooting: Camping 2.0 on CGI on a shared host

2008-07-14 Thread Bluebie, Jenna
We are talking about cgi here, not fast cgi. Specifically CGI's interactions with mod_rewrite in apache. ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list