HEAD HTTP Origin: Network OSI layer 7 · Application Last updated 18 Nov 2026

HEAD request returns a different status or headers than GET

Monitors and link checkers using HEAD see errors (405, 404, different length), while GET works in the browser.

Exact message you may see HEAD request returns 405HEAD returns 404 but GET worksHEAD request different response than GETlink checker HEAD 403405 Method Not Allowed on HEAD
Seen on: HTTP Nginx PHP

Meaning

Some apps, frameworks and WAFs don't implement HEAD correctly: they return 405/403, omit Content-Length or run different code paths. Make HEAD behave like GET without the body, allow HEAD in the router and proxy, and fall back to GET in checkers.

Common causes

  • Route only registered for GET
  • WAF/proxy blocking HEAD
  • Different Content-Length from GET
  • Cache keyed differently for HEAD
  • Monitoring tool using HEAD

⚡ Quick fix

  1. Allow HEAD wherever GET is allowed
  2. Compare curl -I with curl -X GET -I
  3. Make monitors fall back to GET

Detailed fix by platform

cURL

  1. bash
    curl -sI https://example.com/page | head -3
    curl -s -o /dev/null -D - https://example.com/page | head -3

How to diagnose

  1. HEAD status — Same as GET?
  2. Router — Allows HEAD?
  3. WAF — Blocks HEAD?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

102 — HTTP 102 Processing (HTTP)102201 — HTTP 201 Created (HTTP)201202 — HTTP 202 Accepted (HTTP)202203 — HTTP 203 Non-Authoritative Information (HTTP)203405 — HTTP 405 Method Not Allowed (HTTP)405405 — 405 Method Not Allowed on OPTIONS (CORS preflight) (HTTP)405expiry — Certificate expired unexpectedly — manual renewal missed or automation failing silently (SSL / TLS)expiryModSecurity: Access denied with code 403 — Nginx/Apache: ModSecurity: Access denied with code 403 (phase 2). Matched "Operator GE matched 5 at TX:anomaly_score" (Nginx / Apache)ModSecurity: Access d…HEAD

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.