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 UTC-5, David Phillips wrote: > > 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 admin interface. > > This is harder to solve because https access works locally. It's only on > the production apache server (on Elastic Beanstalk) that it fails. > > Can anyone suggest a strategy to find the cause? A quick survey of the > gluon code didn't turn up any obvious place to look. > > Thanks. > > David > > > > On Monday, September 17, 2012 4:18:34 PM UTC-5, Richard wrote: >> >> This is nicer way of restoring it :) >> >> Thanks Bruno! >> >> Richard >> >> On Mon, Sep 17, 2012 at 3:50 PM, Bruno Rocha <[email protected]> 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('123456',443)" >>> >>> -- >>> >>> >>> >>> >> >> --
