On Wed, Oct 12, 2011 at 22:20, Nokan Emiro uzleep...@gmail.com wrote:
It seems to me that PATH_INFO is still not properly handled, but that
it's always empty.
You are right, PATH_INFO is always empty. If I fill it with the
$SCRIPT_NAME
value, controllers can be accessed again. But links
I might be missing something stupid.. but Passenger doesn't like __END__
http://pastie.org/2689517
Same code (omitting requires) fine in Camping server, not with
Passenger/Rack:
compile error config.ru:33: syntax error, unexpected $end, expecting
')' __END__ ^
Works fine under Passenger
SCRIPT_NAME is the mount-path.
PATH_INFO is the internal app-path.
So if you want your application available at xxx.com/my_app/, then the
request xxx.com/my_app/add will look like this:
SCRIPT_NAME=/my_app
PATH_INFO=/add
If it's available at xxx.com/, then xxx.com/add will look like
How can I hide/catch the Camping problem! /xxx not found pages?
It would be great to define my own handler instead, or simply
redirect to the root of my app.
___
Camping-list mailing list
Camping-list@rubyforge.org
On 13.10.2011 20:02, Magnus Holm wrote:
I don't think rackup-files can have __END__.
https://github.com/rack/rack/blob/master/test/builder/end.ru
– Matthias
___
Camping-list mailing list
Camping-list@rubyforge.org
On Thu, Oct 13, 2011 at 21:16, Nokan Emiro uzleep...@gmail.com wrote:
SCRIPT_NAME is the mount-path.
PATH_INFO is the internal app-path.
So if you want your application available at xxx.com/my_app/, then the
request xxx.com/my_app/add will look like this:
SCRIPT_NAME=/my_app
module MyApp
def r404(path)
404: #{path}
# or you can render a template: render :four_oh_four
end
end
There's also r500(klass,method,exception) which gets called when an
exception happens, and r501(method) which gets called when a route is
found, but the controller doesn't have the
7 matches
Mail list logo