Added

• The default behavior when marshalling request headers from the $_SERVER superglobal is to map all entries starting with HTTP_ or CONTENT_ to HTTP headers. However, this behavior is a bit aggressive with regards to the CONTENT_ keys; PHP only maps CONTENT_LENGTH, CONTENT_MD5, and CONTENT_LENGTH in this way. To remain backwards compatible, we are not changing that behavior. However, users who are experiencing conflicts with env variables they have declared (as an example, CONTENT_API_KEY) can define the env variable LAMINAS_DIACTOROS_STRICT_CONTENT_HEADER_LOOKUP. When present, the logic for marshalling headers will only consider exact matches on those three CONTENT_ keys, and ignore any others it identifies. (Behavior for HTTP_ prefixed headers remains the same.)