I don't think that there's a bug. is_https is set because of the http_x_forwarded_proto header, that is an header sent by your webserver back to web2py telling it that the request is coming from an https realm. http_port is set to 80, so it's now totally clear that your setup has a web2py app mounted on the lowest-middleware in your setup (being that gunicorn or whatever else) that is listening on port 80.
BTW, you may be missing that all of this is OUTSIDE the things that web2py can manage: those headers are sent by your frontend and there's nothing web2py can do about it, except treat them as parameters. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
