Can't send json using json:// + notification body.

[gety9]

Describe the bug
Can't send json using json:// + Notification Body, exactly same json load is sent correctly with curl.

Version
Exact version in the top right area: 0.46.04

To Reproduce

Steps to reproduce the behavior:
1, On any watch go to edit > notifications
2, Set the URL to the API in Notification URL List (json://)
3, Set the JSON as required by the API in Notification Body
4, Click on Send Test Notification
5, Click on Notification Debug Logs

Expected behavior
JSON is sent correctly

Screenshots
notification url

notification body

log

exactly same json works fine with curl (response 200)

Tablet (please complete the following information):

• OS: [e.g. iOS] Android 11, server is hosted on termux (android linux)

[dgtlmoon]

Hmm it 100% works (theres an automated test for this) so its likely something in your environment

you did not say anything about how you installed it, docker, etc etc

[gety9]

installed via pip

i saw somewhat similar issue here #2478

[gety9]

Is it fine that json load has single quotes ? (cause validator says it's invalid json)
and that post is made using format = text?

basically issue is that "message" json is not getting unescaped that's why it's marked as invalid dictionary / object. (if you remove escapes then it's valid)

[gety9]

So the topic/subject is wrong, it IS being sent, but the encoding is wrong?

Yes, thank you for correcting me. It's sent but rejected by API cause message field is not valid dictionary or object.

[gety9]

@gety9 this is your answer then, it is written in the UI

It's not that. It's for escaping special characters in string. For test I was using simple numbers 1,2,3,4,5 - they do not need escaping.

But for peace of mind I tried your suggesting - no luck.

[gety9]

Looking at log again it seem to me that problem is that API looks at json passed in message as string and not as json and unnecessarily escapes double quotes. (Or doesn't unescape them after escaping)

But same json works via curl.

[gety9]

Can i add Content-Type header with "application/json" value?
fastapi/fastapi#12390 (comment)

[dgtlmoon]

Can i add Content-Type header with "application/json" value?
fastapi/fastapi#12390 (comment)

Yes

[dgtlmoon]

https://github.com/caronc/apprise/wiki/Notify_Custom_JSON <-- so json:// doesnt do what you think it does

You need post://

@gety9 I also added more logging here - it already tries to apply the application/json header but only if the document parses as json correctly

54a4970

[dgtlmoon]

@gety9 I added an update to the documentation https://github.com/dgtlmoon/changedetection.io/wiki/Notification-configuration-notes#json-style-post--put-requests

do not use json://