Comments (21)
I'm looking into adding this, thanks for the suggestion!
from requests.
Someone was working on this, but I haven't heard from him in a while.
I'd love to see a requests-kerberos
module that provides the auth handler.
from requests.
Was there a published tree with a starting point for this? Else if it's free I may take a stab.
from requests.
Release v0.13.4 includes this (just add auth=requests.auth.HTTPKerberosAuth() to the keyword args to requests.get()) so perhaps this can be closed now...
from requests.
🍰
from requests.
Said code appears to have been ripped out in 377078b
from requests.
correct, there is now a requests-keroberos project which will contain this functionality
https://github.com/requests/requests-kerberos
from requests.
Which doesn't work, and when fixed will continue to rot when you change an interface.
Which isn't packaged by anyone and will be that much more effort to get into e.g. debian or ubuntu.
Security should never be a secondary feature that you have to go to extra lengths to enable.
from requests.
The interface will never change. It was removed because I cannot maintain it.
from requests.
(I apologize if this is coming across a bit confrontational, but I was unreasonably annoyed by the functionality I was wanting and expecting being removed in a commit labelled "hooks and such")
from requests.
refactors are brutal :)
from requests.
I say this about interfaces from the perspective of having made the code work again; some of the details of how the response hook is called appears to have changed since it was written.
I appreciate that this sort of thing is hard to maintain, but that's a reason to say "hey can someone write me a test" not quietly delete it in the apparent hope that nobody notices.
from requests.
this was not quietly removed, requests was basically fully rewritten and stripped down of everything unnccesary.
http://kennethreitz.org/exposures/announcing-requests-v1-0-0
from requests.
Oops, I completely failed to find that. I apologize for my implication.
Still, authentication methods ought to be core functionality and tested along with everything else; anything more complex than Basic is going to end up having to fiddle around behind the scenes.
from requests.
The authentication interface and mechanism is a first-class citizen. Basic and Digest is all that will be supported in core.
from requests.
"Security is hard, batteries not included"
from requests.
Pull request for requests_kerberos sent.
from requests.
@kcr: The biggest problem requests-kerberos has is a lack of tests. If you want to contribute a test suite (or even just a couple of tests), that will greatly improve our ability to keep it up to date. =)
from requests.
@Lukasa I suspect we'll be able to repurpose at least the setup parts of the Zephyr test suite we're working on over the next couple of weekends, we'll definitely be in touch about that :)
from requests.
@eichin, link for the curious?
from requests.
Also, can we move this over to requests/requests-kerberos#1?
from requests.
Related Issues (20)
- Requests post not working with long processing time. HOT 1
- Possible regression with how MaxRetryError is handled HOT 2
- Improper URL serialization of boolean GET parameters HOT 2
- Weird behaviour with https and proxy authentication HOT 4
- "Recommended Packages and Extensions" page asyncio recommendations are outdated
- Status Code 425 named incorrectly HOT 4
- (Caused by ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 400 Bad Request'))) HOT 1
- The Content-Length header for string `data` counts Unicode characters in the string when it should count encoded bytes HOT 6
- Cannot run tests locally HOT 2
- Failed to establish a new connection: [Errno -2] Name or service not known HOT 1
- Local (and build) tests failing HOT 2
- Is it possible to send async generator as `data` argument of request method? HOT 1
- affected urllib3 and certifi packages (older version keeping in setup.py file) HOT 1
- Since migration of urllib3 to 2.x data-strings with umlauts in a post request are truncated HOT 1
- the first response history url is incorrect HOT 1
- Links at docs site return 404 HOT 3
- I don't think the name of this function is appropriate, because the return value of this function is a ConnectionPool object, and the first sentence of the comment is also wrong, which makes it a huge difficulty for me to read!! HOT 2
- Unexpected `UnicodeError` on some URL HOT 2
- python requests.get() stuck HOT 1
- How to use multiple redundant hosts HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from requests.