Skip to content

Add streaming content type header info to docs

What does this MR do and why?

Streaming audit event destination by default uses the content-type header of application/x-www-form-urlencoded. But his can be overridden by using customer headers. This is not clearly documented.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Nate Rosandich

Merge request reports

Loading