Thank you Niphlod, as always :)
I've seen your answer in the other post. Sorry for my lack of knowledge :P
Now I understand better.
I was dealing today with a strange error: the same code worked ok when I
run the app with web2py's embedded server, but the app couldnt connect to
redis when I
see the other thread. accessing redis through an ssl channel just encrypts
the traffic from your frontend to the redis instance: it has nothing to do
with how a user accesses your app (i.e. https or http).
On Wednesday, September 28, 2016 at 9:42:28 PM UTC+2, Lisandro wrote:
>
> I think I know
I think I know what's going on.
I've found this post from Niphlod regarding new redis cache:
https://groups.google.com/forum/#!searchin/web2py/redis$20unavailable$20instance%7Csort:relevance/web2py/x1CCFWflmV8/POdMQmcYEgAJ
There he says: "...want to connect to redis through ssl (previously
I was using an old web2py version
(2.10.3-stable+timestamp.2015.04.02.21.42.07), but today I've updated to
the last stable (2.14.6-stable+timestamp.2016.05.10.00.21.47).
I've seen that in the new version of redis_cache the usage has changed.
Before it was like this:
from
Try look whether a instance of Redis return a type of redis , it is like
that redis connection are failing and returning a string intead redis
object. I Think.
Em quarta-feira, 28 de setembro de 2016 11:24:10 UTC-3, Lisandro escreveu:
>
> Hi there!
> Recently I've updated web2py to the last
5 matches
Mail list logo
