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

Security scan: HTTP TRACE / TRACK method enabled

The server answers TRACE requests, which a scanner flags as a cross-site tracing risk.

Exact message you may see HTTP TRACE method enabledTRACE and TRACK methods are enabledHTTP TRACE / TRACK Methods AllowedCross-site tracing XST
Seen on: HTTP Apache IIS

Meaning

TRACE echoes the request back and can expose headers such as cookies or auth tokens in XST attacks. Disable it: Apache TraceEnable off, nginx only allows GET/HEAD/POST by default (check proxies and app servers), IIS request filtering verb deny.

Common causes

  • Apache default TraceEnable on
  • Application server or proxy allowing TRACE
  • Old IIS/Tomcat config
  • Load balancer forwarding TRACE
  • Scanner reporting TRACK too

⚡ Quick fix

  1. Apache: TraceEnable off
  2. Deny TRACE/TRACK at the proxy or WAF
  3. Re-scan: curl -i -X TRACE https://example.com/

Detailed fix by platform

Apache

  1. TraceEnable off

How to diagnose

  1. TRACE — Answered 200?
  2. Layer — Apache, proxy or app?
  3. Re-scan — Clean?

🔧 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):

1005 — Cloudflare Error 1005: Access denied — The owner of this website has banned the autonomous system number (ASN) your IP address is in (Cloudflare)10051006 — Cloudflare Error 1006 / 1007 / 1008: Access denied — Your IP address has been banned (Cloudflare)10061009 — Cloudflare Error 1009: Access denied — The owner of this website has banned the country or region your IP address is in (Cloudflare)10091010 — Cloudflare Error 1010: The owner of this website has banned your access based on your browser's signature (Cloudflare)10101011 — Cloudflare Error 1011: Access denied (Hotlinking denied) (Cloudflare)10111012 — Cloudflare Error 1012: Access denied (Cloudflare)10121015 — Cloudflare Error 1015: You are being rate limited (Cloudflare)1015102 — HTTP 102 Processing (HTTP)102TRACE

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.