On Dec 13, 2011, at 5:22 PM, pbreit wrote: > Yeah, he's going to need to first script a login so he can grab and store the > cookie which he is then going to need to present on each urllib.urlopen(). > > Being logged in on your browser is not going to help since your browser and > your web2py code are totally separate.
Is that true? I was thinking that if the urllib2 request is being made off a browser request, the existing cookie could be used to effectively run the urllib2 request under the existing authentication umbrella. If the whole sequence is triggered from a post-authentication browser request... > > He could possibly make it easier by not protecting the functions with > Web2py's authentication and instead inserting a secret header or cookie > variable or arg/var.
