Hello-
I just upgraded from v1.65.0 to v1.65.5 today and noticed that I could
no longer log in to one of my controllers using wget's "--auth-no-
challenge" option. After digging through the code, I see that there
are two new lines that were introduced into the /gluon/tools.py file
which cause the problem, and I've commented them out in this snippet:
def basic(self):
request = self.environment.request
### if not self.settings.allow_basic_login:
### return False
basic = self.environment.request.env.http_authorization
if not basic or not basic[:6].lower() == 'basic ':
return False
(username, password) = base64.b64decode(basic[6:]).split(':')
return self.login_bare(username,password)
With these two lines commented out, I can successfully log in using
wget and have a script interact with web2py's interfaces. But when
these two lines are activated, I get redirected to a login page, in
spite of sending the username and password using wget. Please let me
know if this breakage is something that can be fixed in web2py's
current code, or if I need to change any settings on my end to work
with the changes. Hopefully there is not a conflicting objective that
requires it to act this way.
Thanks
Dan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
