contenttype modifier doesn't match Content-Type headers with parameters

[anfragment]

The Content-Type header values can potentially contain parameters after a semicolon, in addition to the media type. Our $contenttype modifier implementation doesn't take that into account.

References:

• https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Type

[anfragment]

In case anyone wants to work on this, I can walk you through a solution.

[Noahnut]

I think I can try

[anfragment]

@Noahnut thanks for offering help, but it turns out $contenttype determines the type base on requests' Sec-Fetch-Dest header instead of response's Content-Type. The issue is incorrect.