mirror of
https://github.com/proxmoxer/proxmoxer.git
synced 2026-04-25 07:06:00 +03:00
[GH-ISSUE #164] InsecureRequestWarning #87
Labels
No labels
backend:https
backend:local
backend:openssh
backend:ssh_paramiko
pull-request
status:ansible-issue
status:help-wanted
status:info-needed
status:proxmox-issue
status:review-needed
type:bug 🐞
type:dependency ⛓️
type:docs 📝
type:enhancement ⏫
type:maintenance 🛠️
type:meta
type:question ❓
type:request ✋
type:testing 🧪
version:1.x
version:latest
version:py2
version:py3
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/proxmoxer#87
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @FrancoTampieri on GitHub (Apr 26, 2024).
Original GitHub issue: https://github.com/proxmoxer/proxmoxer/issues/164
Originally assigned to: @jhollowe on GitHub.
Python 3.12.3
proxmoxer 2.0.1
Even I put in the connection string the verify_ssl=False the error is everytime rased.
Can u take a look?
@jhollowe commented on GitHub (Apr 27, 2024):
Based on the urllib3 docs, you can use the following to disable these warnings:
or just
This warning comes from (recent versions of) the libraries used for making HTTPS connections and can't be changed within proxmoxer.
@FrancoTampieri commented on GitHub (Apr 27, 2024):
Thank you that's works like a charm!
Did u consider to switch from requests to https? I did the switch in some project and was very nice, and I can use it with asyncio.
Regards
Franco
@jhollowe commented on GitHub (May 1, 2024):
What library is that? do you have a link to it?
@FrancoTampieri commented on GitHub (May 7, 2024):
Sure, is that library:
https://www.python-httpx.org
Kind regards
@jhollowe commented on GitHub (May 8, 2024):
Interesting. Considering all the
requests-specific code we have in the app and in the test suite, I think we will stick withrequestsfor now. But this is a very cool project and if it becomes more broadly supported we may consider switching to it.