On Sep 3, 1:53 am, Adam Atlas <[EMAIL PROTECTED]> wrote: > Is there a reason why webapi.py (lines 272 and 280) tries to get > REAL_SCRIPT_NAME from os.environ instead of the local WSGI `env` > variable? It seems like the current way would only work if you're > using it directly through CGI. I'm running in Apache + mod_wsgi, and > I don't see how it could be passed in the actual process environment > (or why it should be, considering that it would apply to the entire > Apache process).
What purpose does REAL_SCRIPT_NAME serve anyway? I ask as it isn't a standard CGI variable, nor required by WSGI. It seems perhaps to be a hack to workaround problems with some WSGI adapters which doesn't set SCRIPT_NAME correctly. So, when would you actually use it? Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
