Thomas Broyer ha scritto:
On Sun, Dec 14, 2008 at 11:23 AM, Manlio Perillo wrote:
In my WSGI applications I always have an ending slash to the URLs.
This means that an URL without the ending slash will cause the underlying
resource to return 404 Not Found HTTP response.
What is the best method
Randy Syring ha scritto:
Manilo,
Manlio not Manilo, please!
Here is a thread on this topic, well a partial thread, start reading
about half way down:
http://groups.google.com/group/pylons-discuss/browse_thread/thread/6888b790239b488b
I found it informative.
Thanks, it is interesting
Manilo,
Here is a thread on this topic, well a partial thread, start reading
about half way down:
http://groups.google.com/group/pylons-discuss/browse_thread/thread/6888b790239b488b
I found it informative.
--
Randy Syring
RCS Computers & Web Solutions
502-
On Sun, Dec 14, 2008 at 11:23 AM, Manlio Perillo wrote:
>
> In my WSGI applications I always have an ending slash to the URLs.
> This means that an URL without the ending slash will cause the underlying
> resource to return 404 Not Found HTTP response.
>
> What is the best method to handle this, us
Hi.
In my WSGI applications I always have an ending slash to the URLs.
This means that an URL without the ending slash will cause the
underlying resource to return 404 Not Found HTTP response.
What is the best method to handle this, using a regex based URL dispatcher?
I'm planning to add an o
