It might not be 100%. For example, on Nginx, you have to include this
config:
uwsgi_param UWSGI_SCHEME $scheme;
But I still don't really understand why you need this.
On May 24, 2011, at 5:47 PM, Anthony wrote:
> On Tuesday, May 24, 2011 6:34:15 PM UTC-4, Massimo Di Pierro wrote:
> In trunk we have
>
> request.is_https
>
> Which checks whether request.env.wsgi_url_scheme is https (or HTTPS) or
> request.env.https is "on".
>
...and of course doesn't necess
On Tuesday, May 24, 2011 6:34:15 PM UTC-4, Massimo Di Pierro wrote:
>
> In trunk we have
>
> request.is_https
Which checks whether request.env.wsgi_url_scheme is https (or HTTPS) or
request.env.https is "on".
In trunk we have
request.is_https
Massimo
On May 24, 4:33 pm, Andrew Thompson wrote:
> On 5/24/2011 5:02 PM, pbreit wrote:
>
> > Does " request.env.https" exist? I don't see it in my environment.
>
> It does for me, running web2py behind lighttpd.
>
> I also found a reference to request.env.wsg
On 5/24/2011 5:02 PM, pbreit wrote:
Does " request.env.https" exist? I don't see it in my environment.
It does for me, running web2py behind lighttpd.
I also found a reference to request.env.wsgi_url_scheme, but I wasn't
sure if it's content could be 99+% predicted.
http://comments.gmane.or
Does "request.env.https" exist? I don't see it in my environment.
I don't think https is necessary for those links. And if it is, your web
server or code should be enforcing SSL on the URLs.
6 matches
Mail list logo
