HTTP 414 / 404.15

IIS request-length limits break SCEP (414 / 404.15)

Last reviewed 2026-07-18 by the Just Software engineering team ยท also seen as 414 request-uri too long, 404.15 query string too long, maxquerystring ndes

What it means

SCEP clients send certificate requests as very long base64 blobs in the URL query string. Default IIS request-filtering limits (maxQueryString, maxUrl) and HTTP.SYS header limits are far too small for this, so requests die with HTTP 414 (Request-URI too long) or IIS request-filtering rejections such as 404.15 (query string too long) before NDES ever sees them. This is a required configuration step for NDES with Intune, not an optional tweak.

Common causes

  1. NDES installed without applying the request-length configuration from the Intune NDES setup documentation.

  2. A rebuilt or replacement NDES server where the IIS limits were forgotten.

  3. A reverse proxy or load balancer in front of NDES imposing its own URL-length limit even though IIS is configured correctly.

How to fix it

  1. Raise IIS request filtering limits: %windir%\system32\inetsrv\appcmd.exe set config /section:requestfiltering /requestlimits.maxquerystring:65534 and ... /requestlimits.maxurl:65534.

  2. Raise HTTP.SYS limits: under HKLM\SYSTEM\CurrentControlSet\Services\HTTP\Parameters, set MaxFieldLength and MaxRequestBytes (DWORD) to 65534, then reboot the server.

  3. Check the IIS log for the actual sub-status (414, 404.15, 404.14) to confirm which limit is firing.

  4. If a proxy/WAF fronts NDES, raise its URL and header length limits too โ€” F5, NetScaler and cloud WAFs all have their own defaults.

An unhandled error has occurred. Reload ๐Ÿ—™