However when i try to access the pylons application all links which were
created with the pylon’s url object are messed up (double slash “//” at
the beginning instead of one slash “/”)
If i use following code to generate the url for the current pylons
“page”:
${h.url.current()}
I get “//CURRENT_URL” instead of “/CURRENT_URL”
I tried it even with a fresh pylons app, to make sure that none of my
routing entries are responsible for this behavior.
It seems that the SCRIPT_NAME “/” is added at the beginning of each URL
somehow.
I don’t think my problem is related to the uWSGI Server because when i
try to access the uWSGI served pylons app via Cherokee the links are
fine.
I would be thankful for any ideas or hints.
I used following versions:
nginx: 0.8.47-0
uWSGI: 0.9.5.4
pylons: 1.0 (but same problem with 0.9.7)
On Tue, Aug 03, 2010 at 10:11:36AM -0400, timeu wrote:
If i use following code to generate the url for the current pylons
It seems that the SCRIPT_NAME “/” is added at the beginning of each URL
nginx: 0.8.47-0
uWSGI: 0.9.5.4
pylons: 1.0 (but same problem with 0.9.7)
I tried that actually but when I remove this entry from the nginx.conf,
Pylons complains that the SCRIPT_NAME key in the request dict is missing
(I can post the error message later)
If I just add the uwsgi_param SCRIPT_NAME entry without the “/” nginx
wont’t start.
