0
Uptime monitor fails assertion for 301; will pass assertion when set to expect 200
Source: getsentry/sentry#116635 · opened by @emalone-acorn
Environment
SaaS (
Steps to Reproduce
1. Set up a new uptime monitor
* Method: GET
* URL:
* Verification: Status Code = 301
2. Click 'Test Monitor' button
Expected Result
Assertion passes so that I can enable the monitor
Confirmed from CURL that the response is 301
Actual Result
Assertion fails (see bottom right)
<img width="1457" height="821" alt="Image" src=" />
Product Area
Alerts
Link
DSN
_No response_
Version
_No response_
SaaS (
Steps to Reproduce
1. Set up a new uptime monitor
* Method: GET
* URL:
* Verification: Status Code = 301
2. Click 'Test Monitor' button
Expected Result
Assertion passes so that I can enable the monitor
Confirmed from CURL that the response is 301
Actual Result
Assertion fails (see bottom right)
<img width="1457" height="821" alt="Image" src=" />
Product Area
Alerts
Link
DSN
_No response_
Version
_No response_
No pledges yet. Be the first to back this.
Comments
Similar requests
Support Uptime Monitor for % Monthly Uptime on Insights Uptime Page
0 votes · 0 comments
Identity Assertion JWT Authorization Grant (ID-JAG) Support
2 votes · 0 comments
SAML2 Assertion Encryption
0 votes · 0 comments
Cron issues not triggering issue webhooks
0 votes · 0 comments
Notification for Uptime Monitor after Resolution
0 votes · 0 comments
No comments yet.