[Catalyst] Problems with $c->req->base on lighttpd deployment
Javier Luque Tuason
javier at sixsideddevelopment.com
Thu Jan 17 15:09:47 GMT 2013
Following the instructions for lighttpd deployment:
As well as trying the static deployment here:
I noticed that styles and images on non-root pages were being incorrectly
parsed in the c.uri_for method.
For example in: http://myapp.com/foo/bar
[% c.uri_for('/css/main.css') %]
http://myapp.com/foo/bar/css/main.css (instead of
Upon further inspection I noticed that the problem lied in $c->req->base not
returning the absolute path but instead it returned the relative path.
[% c.req.base %] parsed to: http://myapp.com/foo/bar/ (instead of
This problem does not occur when using the standalond deployment:
Reverting to Catalyst 5.8 fixed this problem but unfortunately there are
other problems. Also not that
myapp_server.pl works perfectly and this only happens when myapp_fastcgi is
Any else experiencing these problems?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Catalyst