Issue
The endpoint I am trying to monitor has specific requirements for the request body. What are the limitations of the "Body" field during an Uptime Monitor's creation?
Applies To
- All SaaS Customers and Self-Hosted users
- Uptime Monitoring
Resolution
Some things to keep in mind are the following:
- There is no direct character limit on the body field itself, but there is an overall HTTP request size limit of 1000 bytes that affects the total size of the uptime monitoring request. The validation uses UTF-8 encoding, so non-ASCII characters count as multiple bytes.
- Uptime requests are constructed as simple HTTP requests, and the body is appended as-is as a string. You can also see that in our code here. Therefore, there is unfortunately no support for alternative forms of data like binary data or multipart boundaries.