HTTP: Non-Encoded Binary Detected In URLEncode Content Type

This signature detects for conformance to RFC 1738 that specifies the handling of URL-Encoded data. If a client specifies a Content-Type of URL-Encoded, any binary data - including Unicode characters - should be properly encoded. This signature will trigger on both malicious abuse of this standard as well as mis-configured clients and web applications.

Short Name

HTTP:AUDIT:BINARY-IN-URLENCODE