B.4 Content-Encoding Header

NRF does not accept incoming request messages in gzipped format for NFManagement service operations such as NFRegister, NFUpdate (Complete/Patch Replacement, Heartbeat), and NFStatusSubscribe (both New and Update Subscriptions).

If the Content-Encoding header is present and has an unsupported value, NRF rejects the HTTP request with 415 Unsupported Media Type error, NRF only accepts the Content-Encoding header value set to “identity”. In such error cases, NRF will include an Accept-Encoding header with the value set to “identity.”

If the Content-Encoding header is missing but the payload is still compressed, NRF rejects the HTTP request with a 400 Bad Request error due to the invalid message.

However, NRF supports gzipped encoding for response messages for JSON body in NFManagement service operations such as NFRegister, NFUpdate (Complete/Patch Replacement, Heartbeat), NFListRetrieval, and NFProfileRetrieval, provided that the client (NF) specifies the gzip format in the Accept-Encoding header when requesting response.