That "urlencoded" encoding is used by the browser on post data when the request content-type is “application/x-www-form-urlencoded”.
When you see this content-type, the Sniffer parses the post data into request fields and sends the request fields on to the Archiver (NOTE: in this case, the raw request content is NOT sent to the Archiver). The “Max Hit Detail Size” limit is imposed on the RequestFIelds by the Sniffer before sending them to the Archiver. When the Archiver receives the request fields, it decodes them before storing in the database (that makes it easier to view). Since we don’t know how many characters may be encoded (if any), the example in the doc show the worst case scenario where every character is encoded. The encoding requires 3 characters to represent each character.
The following explains some terms in a Hit details and Traffic Analysis Options.
RequestTotalBytes = Total amount of bytes in an HTTP request. This includes headers and content (post data), if present.
RequestContentSize = Size of the HTTP request content (i.e. the post data).
Content-Length header = This is defined by the HTTP protocol as the size of the request content (i.e. post data). It may not always be present.
MaximumRequestSize = The maximum size of the request content. This is imposed by the Sniffer on the request content (post data) if it is being sent to the Archiver.
Request content is often referred to as “post data”. If the content-type is “application/x-www-form-urlencoded” or “multipart/form-data”, the Sniffer parses the data into request fields and send the request fields to the Archiver. The raw request content is not sent. If the content-type is anything else, the “Maximum Request Size” limit is imposed on the data and it is sent to the Archiver.
