Try:
SetEnvIf X-Forwarded-Proto https HTTPS=1
I had a similar issue and posted on the wsgi group:
https://groups.google.com/forum/?fromgroups=#!topic/modwsgi/Egi6pg7c2X8
Regards,
Andrew
On Tuesday, September 18, 2012 2:19:41 PM UTC-5, David Phillips wrote:
>
> Thanks for checking,
Apache is an big beast, zillions of options...
It could that HTTPS env var in apache is not passed to WSGI. Check:
https://httpd.apache.org/docs/2.2/mod/mod_ssl.html#ssloptions
StdEnvVars must be enabled
mic
2012/9/18 David Phillips :
> Thanks for checking, Massimo. I'll start looking into t
Thanks for checking, Massimo. I'll start looking into the web server.
David
On Sep 18, 2012, at 1:30 PM, Massimo Di Pierro
wrote:
> This confirms my impression. This is not a web2py 2.0.x issue. Something else
> has changed. env.wsgi_url_scheme and env.https are from the WSGI environment.
This confirms my impression. This is not a web2py 2.0.x issue. Something
else has changed. env.wsgi_url_scheme and env.https are from the WSGI
environment. HTTPS is not defined and WSGI_URL_SCHEME is http.
I am suing web2py 2.0.9 with apache and I get
request.env.wsgi_url_scheme: https
reques
Sure.
[Tue Sep 18 15:49:25 2012] [error] WARNING:root:request.env.wsgi_url_scheme:
http
[Tue Sep 18 15:49:25 2012] [error] WARNING:root:request.env.https: None
On Sep 18, 2012, at 10:40 AM, Massimo Di Pierro
wrote:
> Can you please print the values of
>
> request.env.wsgi_url_scheme and re
Can you please print the values of
request.env.wsgi_url_scheme and request.env.https
It will help me understand what is going on. I do not think we changed the
request.is_https behavior. web2py my not be able to detect https if behind
a proxy.
Massimo
On Tuesday, 18 September 2012 10:27:34 U
Thanks to everyone for their replies. Bruno, that is a neat trick.
Unfortunately, it didn't solve my problem. I generated a new password and
restarted the apache server, but I am seeing the same behavior --
request.is_https is returning false even though I am using https and I
cannot use the ad
This is nicer way of restoring it :)
Thanks Bruno!
Richard
On Mon, Sep 17, 2012 at 3:50 PM, Bruno Rocha wrote:
> assuming your webserver user is www-data and desired password 123456
>
> cd path/to/web2py
>
> sudo -u www-data python -c "from gluon.main import save_password;
> save_password('123
assuming your webserver user is www-data and desired password 123456
cd path/to/web2py
sudo -u www-data python -c "from gluon.main import save_password;
save_password('123456',443)"
--
You probably had erase you parameters.py file when you install the new
version... Did you made a backup?
If so, just copy/paste the 443 parameters py files from the archive into
the web2py folder of the new 2.0.8 installation.
If you didn't make a backup, what you can do is in order to create a n
I had a web2py 1.99.7 app running on Elastic Beanstalk. I was able to use
the admin interface over https. I then upgraded web2py to 2.0.8 and
uploaded it to EB. Now I am getting this message when I try to access the
admin interface over HTTPS:
ATTENTION: Login requires a secure (HTTPS) conne
11 matches
Mail list logo