Monitors & detections

Use HEAD when headers are enough

Make a lightweight check without requesting response content.

Reviewed

Choose HEAD deliberately

In Request, select HEAD when your endpoint supports it and the response headers/status are enough to assess availability. Not every endpoint handles HEAD in the same way as GET.

Remove body-dependent rules

HEAD cannot send a request body or validate response text and JSON rules. Turn off those rules before saving a HEAD configuration. If you need to inspect a readiness field, use a suitable body-returning method instead.

Inspect the first result

Save and run a manual check. Review the actual response code against Healthy HTTP codes. A method-not-allowed response may mean you should use GET, not broaden healthy codes to accept that error.

A HELPING WING

Let’s find your next step.

Open the chat in the corner to ask a question. Prefer email? Drop us a note and we’ll help you from there.

[email protected]