-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Callling /control/parental/enable failing with only content-type application/json is allowed
#795
Comments
…nt-type application/json is allowed` frenck#795
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. |
This is not stale. Frenck is travelling and unable to action it.
…On Tue, 5 Sept 2023, 18:01 github-actions[bot], ***@***.***> wrote:
There hasn't been any activity on this issue recently, so we clean up some
of the older and inactive issues.
Please make sure to update to the latest version and check if that solves
the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further
activity occurs. Thanks!
—
Reply to this email directly, view it on GitHub
<#795 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADOOKNSHYB4GPNGQT4H3GLXY3L53ANCNFSM6AAAAAA3FUHI5I>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Many of us have been waiting a long time for this fix.... |
…nt-type application/json is allowed` frenck#795
fixed in #796 |
Problem/Motivation
I'm using the AdGuard Home addon in Home Assistant and believe I've traced a bug I'm having to the code in this repository.
Specifically, the call to /control/parental/enable is failing.
Expected behavior
Should be able to enable the parental filtering via the API wrapper.
Actual behavior
Throws an error with:
only content-type application/json is allowed
.Steps to reproduce
leave_front_door_open
and set a port (eg 3001) for the Web interfaceProposed changes
It appears the AdGuard Home API now enforces a "Content-Type: application/json" for the API when a body is present. The request to /control/parental/enable is adding a body but it's not JSON.
From what I can tell from https://github.com/AdguardTeam/AdGuardHome/blob/master/openapi/openapi.yaml the endpoint doesn't actually expect a body.
The fix is to simply remove the data argument on line 36 of parental.py.
The text was updated successfully, but these errors were encountered: