-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
User-Agent should be configurable #385
Comments
tobixen
added a commit
that referenced
this issue
Mar 5, 2024
tobixen
added a commit
that referenced
this issue
Mar 5, 2024
tobixen
added a commit
that referenced
this issue
Mar 5, 2024
tobixen
added a commit
that referenced
this issue
Apr 13, 2024
fixed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ref home-assistant/core#105292 (comment) - it seems like it's possible to set arbitrary headers to be sent in every request initiated through some davclient object, except
User-Agent
and some others. Now it's probably a good idea not to touch theContent-Type
orAccept
-headers, but theUser-Agent
should be possible to configure freely.Also, passing
{}
as default parameter is dangerous, ref https://stackoverflow.com/questions/26320899/why-is-the-empty-dictionary-a-dangerous-default-value-in-pythonThe text was updated successfully, but these errors were encountered: