Re: [web2py] auth.is_logged_in and @auth.requires_signature() under investigation

@weheh, the quick fix would be using custom ajax function instead of using web2py_component. It's meant to be used with server-side LOAD helper. Since you can't create CORS component using LOAD, I'm not sure if web2py_component should work with CORS either. So, instead of calling web2py_component,

Re: [web2py] auth.is_logged_in and @auth.requires_signature() under investigation

Hello, I tried to trace down the problem. If you sign an url on different scheme (http -> https) everything works when opened manually in browser. But when opening it async, for example using $.ajax, current.session is empty. This causes URL.Verify to return False because there is no session.auth

[web2py] auth.is_logged_in and @auth.requires_signature() under investigation

I am dead in the water trying to make an https ajax call from an http session. CORS is enabled on server but the web2py_component https URL with user_signature=True now triggers an erroneous non-logged-in response to auth.is_logged_in() when, in fact, the user is logged in. First, thanks to Mar