FeatureFuel
0

Counterintuitive `Accept`-Header for the `json-query` monitor

Source: louislam/uptime-kuma#4491 · opened by @bcarlock-mycarrier
📑 I have found these related issues/pull requests I wasn't able to find any similar issues. 🛡️ Security Policy • I agree to have read this project [Security Policy]( Description Any time I attempt to use a query I receive Unexpected token < in JSON at position 0 👟 Reproduction steps Create a monitor that uses header authentication with the JSON Query monitor. Given the following JSON response: {"importantnumber":98,"number":0,"failures":8276,"warnings":0,"lastprocessed":"2024-02-14T00:48:15.837Z"} and the JSON query ($.importantnumber < 1000), the response should be "true" ![image]( ![image]( 👀 Expected behavior Monitor should show the status as up. 😓 Actual Behavior Monitor throws an error and cannot get status ![image]( 🐻 Uptime-Kuma Version 1.23.11 💻 Operating System and Arch Ubuntu 22.04 (Kubernetes) 🌐 Browser Brave v1.62.162, Vivaldi 6.5.3206.61 🖥️ Deployment Environment…

No pledges yet. Be the first to back this.

Make a pledge

Pledge your monetary support if this feature is added.

$

Comments

No comments yet.

Replying to

Add a comment

What do you think about this feature request?


Similar requests