-> > The CP-Location trick is not needed (I should remove it from this page -> > as it confuses people). -> -> Hmm, I wrote that part of the page. My specific reason for using a -> custom header is that it's the only way I can see to locate a CherryPy -> application *not* at the root of a virtual host. -> -> For example, if I have a CherryPy application exposed at (say -> http://myserver/myapp/) then how do I write absolute URL paths (like -> "/login" within my app? As far as I can tell, there's nothing -> available to my application that says "/myapp/". Yes, I can hard code -> it in the application, but I'd rather keep the value in one place - -> it's necessary in the Apache config, so I'd like to pass it from there -> to the app. -> -> If I've missed something that I could have used, though, I'd like to -> know (and I'll update the page appropriately).
Doesn't this preclude redeploying your WSGI apps under different drivers, e.g. CGI vs SCGI vs...? I tend to do things like run my Quixote applications under '/url' and '/~t/url.cgi' -- the former for deployment, the latter for testing and development. You would have to have a different Apache rewrite rule for each case, no? I use relative URLs because of this, but I understand why this might cause you problems. Perhaps we can add a 'root namespace' parameter to WSGI... cheers, --titus _______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com