Companion

Default behavior: appends each registered content type that is not already represented in the existing Accept headers. Preserves backward compatibility.

Skips Accept header injection entirely when at least one Accept header is already present on the request. Falls back to Default behavior when none are present. Useful when working with APIs that are strict about which Accept values they accept.