I don't have a SSL yet, so before I get one, users will have an issue when they visit the site. In any case, I better just get the SSL and then I don't have to worry about this. But, still I don't understand the problem. I definitely didn't uncomment it and this issue only happened after I reloaded my app. Now, it's actually fine, back to http not sure what caused it.
On Wednesday, February 24, 2016 at 11:08:10 PM UTC+8, Niphlod wrote: > > why should it be a problem only lord knows, https should be everywhere in > 2016..... but if you have request.requires_https() anywhere it tells to > redirect the request over to https ... > sure you "didn't uncomment it" ? > > On Wednesday, February 24, 2016 at 3:08:08 PM UTC+1, Joe wrote: >> >> I just reloaded my app on Pythonanywhere and after reloading, my site is >> forced to https for some reason. >> All HTTP requests are redirected to HTTPS. I didn't uncomment the >> #request.requires_https() >> Anyone had a similar issue? What is the best way to resolve this? >> >> I asked Python anywhere, they said it "sounds like a web2py config >> thing". The only time I need the https is when I login to the admin as >> Pythonanywhere requires https there. >> When the rest of my URLs are forced to https, it's kind of a problem. >> > -- 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/d/optout.
