RFC 8188, "Encrypted Content-Encoding for HTTP", June 2017

Errata ID: 8621
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Patrick Barrett
Date Reported: 2025-10-30

Section 3.2 says:

   HTTP/1.1 200 OK
   Content-Length: 73
   Content-Encoding: aes128gcm

   uNCkWiNYzKTnBN9ji3-qWAAAABkCYTHOG8chz_gnvgOqdGYovxyjuqRyJFjEDyoF
   1Fvkj6hQPdPHI51OEUKEpgz3SsLWIqS_uA

It should say:

   HTTP/1.1 200 OK
   Content-Length: 74
   Content-Encoding: aes128gcm

   uNCkWiNYzKTnBN9ji3-qWAAAABkCYTHOG8chz_gnvgOqdGYovxyjuqRyJFjEDyoF
   1Fvkj6hQPdPHfNE6ZBBGizjWQMll3XVvzJ8

Notes:

This is the same issue as Erata ID 8620 (https://www.rfc-editor.org/errata/eid8620), but for the next example.

This one I'm less sure about. The RFC never explicitly says whether the final padding delimiter is required or not, but, by my reading at least, does strongly imply it is required in several places.

Assuming the final padding delimiter is required, this example should include it.

Report New Errata