You're using *var with a default value, and the magic *path_info on
top of that. All of these could interact in unexpected ways. It
would be better to make two or three specific routes for these cases,
and to use named routes for generation. That minimizes the ambiguity.
So do something
Looking through the code (and reading the documentation), it turns out
that this is intentional. I've solved the problem by stripping off
the last component of the path in the SCRIPT_NAME environment variable
which gets me up to the root controller, but doesn't mess anything up
if the app is
On Wed, Aug 20, 2008 at 3:59 PM, EricHolmberg
[EMAIL PROTECTED] wrote:
I'm seeing an issue with the usage of path_info (used to adjust the
PATH_INFO and SCRIPT_NAME variables) with url_for(...) which results
in the path leading up to the *path_info showing up as the URL for the
root
I'm seeing an issue with the usage of path_info (used to adjust the
PATH_INFO and SCRIPT_NAME variables) with url_for(...) which results
in the path leading up to the *path_info showing up as the URL for the
root controller. I'm not sure if this is intended. If so, any ideas
on how to get the
