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

Errata ID: 5516
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Dolan Murvihill
Date Reported: 2018-10-05
Held for Document Update by: Francesca Palombini
Date Held: 2022-11-09

Section 3.1 says:

HTTP/1.1 200 OK
Content-Type: application/octet-stream
Content-Length: 54
Content-Encoding: aes128gcm

I1BsxtFttlv3u_Oo94xnmwAAEAAA-NAVub2qFgBEuQKRapoZu-IxkIva3MEB1PD-
ly8Thjg

It should say:

HTTP/1.1 200 OK
Content-Type: application/octet-stream
Content-Length: 53
Content-Encoding: aes128gcm

I1BsxtFttlv3u_Oo94xnmwAAEAAA-NAVub2qFgBEuQKRapoZu-IxkIva3MEB1PD-
ly8Thjg

Notes:

16-bit encrypted payload
16-bit authentication tag
21-bit header

The other example, in Section 3.2, reports the correct content length of 53

Report New Errata