that would only work if the web server can determine if a particular request should be http or https, which it could do only if there was something in the request URI to indicate that (like the URI begnning with /secure for example).
But what if I have an arbitrary URI (e.g. /hello/login) that should redirect to https, but others (e.g. /hello/logout) that should not ? On Jan 2, 3:29 pm, "Bob Ippolito" <[email protected]> wrote: > We do lots of HTTPS with Pylons, we just don't use that decorator. In > our case, HTTP -> HTTPS redirects are done at the web server layer and > not in the application at all. > > On Fri, Jan 2, 2009 at 3:21 PM, Tycon <[email protected]> wrote: > > > So no one is using this decorator for https ?? > > I guess it's only required for serious e-commerce websites, maybe > > there are no such pylons apps > > > On Jan 1, 6:23 pm, Tycon <[email protected]> wrote: > >> This decorator is supposed to redirect HTTP GET requests to HTTPS. But > >> guess what ? The query string in the request URI is lost, so the > >> redirected (https) request will not have any request.params even if > >> the original (http) request did..... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
