Ian Bicking <[EMAIL PROTECTED]> writes: >> All you can do is include that value as parameter instead, or use >> WSGI 2 (which of course doesn't exist yet, but somewhere we've penned >> this 'feature' to be removed in version 2 of the spec). > > It's mentioned as an issue that WSGI 2 could address, but there hasn't > been any proposed solution.
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? -- Yannick Gingras --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
