louislam / uptime-kuma

A fancy self-hosted monitoring tool

Home Page:https://uptime.kuma.pet

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Regarding the escape characters in Webhook requests.

JasonVei opened this issue Β· comments

⚠️ Please verify that this question has NOT been raised before.

  • I checked and didn't find similar issue

πŸ›‘οΈ Security Policy

πŸ“ Describe your problem

The issue encountered: In the same Webhook notification configuration, the notifications from the Monitor Group work properly, but the notifications from the General Group do not work properly;

  1. I have previously searched and found that you provided an answer to a similar issue, which requires adding Content-Type: application/json; application/x-www-form-urlencoded; to the Headers or modifying the User-Agent. I have tried these in the test and they indeed solved the problem;
  2. However, I found that the webhook service I am using can only support the Content-Type of application/json type, other types cannot be supported to output normally (because it is a program specified by the company to be used, so it cannot be replaced for the time being);

I look forward to a direction for processing in your spare time, thank you. πŸ™

πŸ“ Error Message(s) or Log

Monitor Group
image-20240703162712188


General
image-20240703162733789

🐻 Uptime-Kuma Version

Version: 1.23.13

πŸ’» Operating System and Arch

WSL: ubuntu 20.04 x86

🌐 Browser

Microsoft Edge 126.0.2592.87 x64

πŸ–₯️ Deployment Environment

  • Runtime: Docker version 27.0.2, build 912c1dd
  • Database:
  • Filesystem used to store the database on: Windows on a ssd
  • number of monitors: 40

We are clearing up our old help-issues and your issue has been open for 60 days with no activity.
If no comment is made and the stale label is not removed, this issue will be closed in 7 days.