disable warning #2271
Merged
disable warning #2271
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
benderl
force-pushed
the
disable-request-warning
branch
3 times, most recently
from
5398b90 to
db0b912
Compare
benderl
force-pushed
the
disable-request-warning
branch
from
db0b912 to
c6e20db
Compare
LKuemmel
approved these changes
Apr 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Wenn ein HTTPs-Request mit abgeschalteter Zertifikatsprüfung (
verify=False) ausgeführt wird, meldeturllib3, dass dies ein Sicherheitsproblem ist. Bei der Abfrage von lokalen Geräten kommt es jedoch häufig vor, dass die Zertifikate selbstsigniert sind und nicht automatisch geprüft werden können.Damit nicht in jedem Regeldurchlauf eine oder sogar mehrere Logmeldungen generiert werden, wird diese mit dem PR temporär deaktiviert, wenn der Parameter
verify=Falseübergeben wird.Eine andere Alternative wäre ein angepasster SSL-Context. https://scrapingant.com/blog/requests-ignore-ssl#using-custom-ssl-contexts-in-python
Ticket #72387823