#594: TracError: KeyError: 'SCRIPT_NAME'
------------------------+--------------------
Reporter: tim | Owner: nobody
Type: defect | Status: new
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords: wsgi
------------------------+--------------------
Changes (by olemis):
* keywords: => wsgi
Comment:
Replying to [ticket:594 tim]:
> After migrating from 0.5.3 to 0.6 I am getting errors when accessing
certain pages. The error simply says {{{TracError: KeyError:
'SCRIPT_NAME'}}}.
>
More information is needed so as to reproduce this issue , figure out
what's wrong and fix these errors . Do you see any error messages in the
log ? Any tracebacks ?
> I'm using uwsgi and nginx to serve pages. I modified nginx to include
{{{uwsgi_param SCRIPT_NAME '';}}}
You should not be doing so considering the [pep:333#environ-variables
purpose of SCRIPT_NAME var].
> to try working around the problem, but I'm wondering if this is why I'm
having other problems accessing existing tickets.
Could you please mention what kinds of problems ?
> 0.5.3 didn't require me to have that line in the nginx config, too.
>
AFAICT this should not be necessary. Updating `SCRIPT_NAME` is a
responsibility of the web server . Maybe this is an issue specific to
nginx ?
> Incidentally, there's no 0.6 option in the Version dropdown on this bug
tracker.
Eventually ...
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/594#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
