#594: TracError: KeyError: 'SCRIPT_NAME'
---------------------------+-------------------------
Reporter: tim | Owner:
Type: defect | Status: review
Priority: critical | Milestone: Release 7
Component: multiproduct | Version: 0.6.0
Resolution: | Keywords: wsgi, hooks
---------------------------+-------------------------
Comment (by olemis):
Replying to [comment:14 tim]:
> Replying to [comment:1 olemis]:
> > Replying to [ticket:594 tim]:
> > > 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:0333#environ-variables
purpose of SCRIPT_NAME var].
>
> After doing a lot of reading... It seems like SCRIPT_NAME should always
be an empty string in my case since I'm running bloodhound in the root
path.
That would be the case for the global environment .
> Shouldn't the product url's be part of the PATH_INFO as it's the
"virtual location" '''within''' the application.
For products no . The reasons for doing so are documented in bep:0003 . In
a few words in order to achieve backwards compatibility with ''Trac'' code
the multi-product architecture is a reimplementation of
[wiki:Proposals/BEP-0003/MultienvParentDir this deployment] within a
single ''Trac'' environment powered by what we named [bep:0003#product-
envs product environments]. The later are self contained units equivalent
to ''Trac'' (i.e. global) environments . All this implies that product
environments expect `PATH_INFO` to be set to /wiki , /ticket , ... in
spite of dispatching requests to the right handler . That's why the whole
path is shifted to the left like shown [http://bhnet.blood-
hound.net/browser/bloodhound/bloodhound_multiproduct/multiproduct/hooks.py?marks=69-72#L69
here]
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/594#comment:18>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
