Mike Orr wrote: > On Wed, Apr 30, 2008 at 6:21 AM, Ian Bicking <[EMAIL PROTECTED]> wrote: > > > > Yannick Gingras wrote: > >> Ian Bicking <[EMAIL PROTECTED]> writes: > >> For this particular problem, I can work around the slashes collapsing > >> with a regexp but it would indeed be nice to have a general workaround > >> in WSGI 2. Where is it discussed? > > > > Discussion happens on the Web-SIG mailing list, though there hasn't been > > any discussion lately. There's also the wiki page: > > http://wsgi.org/wsgi/WSGI_2.0 > > On the page it says SCRIPT_NAME, PATH_INFO, and QUERY_STRING are > recommended for removal. How would url_for() be able to recreate the > URL without them? More to the point, how could Routes or Pylons work > at all without PATH_INFO: you wouldn't know which controller to route > to. > > And REMOTE_ADDR and SERVER_SOFTWARE: the application may want > REMOTE_ADDR for authentication or logging, and SERVER_SOFTWARE is > theoretically useful if the app wants to modify its behavior according > to the server.
Hmmm, I wander if the page is just badly worded. Maybe they meant that 'optional' designation be removed, thereby making them mandatory. Wouldn't be practical not to have them. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
