The problem is NOT about how to setup apache to redirect http to https. I am already doing that. But, in fact, it was such a redirection, combining with the unfortunate fact that web2py's URL(..., scheme=True) still generating "http://..."; links, causing my RESTful API to malfunction. Who would know an http PUT request would lost its http body after a redirection? Nonetheless, in my previous post, I already narrowed down to the root cause, and asked: why URL(..., scheme=True) is currently implemented as detecting wsgi_url_scheme env var, rather than simply relying on the more sophisicated request.is_https?
Regards, Ray On Tuesday, July 16, 2019 at 2:18:45 PM UTC-7, Paco Bernal wrote: > > You can always redirect apache from http to https -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/e6a3c5f0-2076-4182-a95c-26c212fe56e0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
