Don't require specific Content-Type header when Protobuf rule is defined for URL

[carstenhag]

Description

My responses have the Content-Type "application/vnd.mapbox-vector-tile" (https://github.com/mapbox/vector-tile-spec). Even though I properly configured Protobuf for the URL path, the previewer did not show the decoded response body:

To circumvent this, I had to add script that changes the header: response.headers["Content-Type"] = "Content-Type: application/protobuf";

Why this feature/change is important?

It would make it easier to decode Protobuf, as right now a custom script is needed in some cases.

Context

Protobuf Settings / rule:

[NghiaTranUIT]

it's correct, because we only decode it with the protobuf if the content type is protobuf

[NghiaTranUIT]

After changing the Content-Type by the Scripting, does it work? @carstenhag

[carstenhag]

Yep, after the script change it's fine. My point is: It shouldn't be necessary; I already specified the Protobuf URL.

Maybe a checkbox (Ignore content type, always assume Protobuf response for this URL Path) would solve my needs & not introduce negative effects

[NghiaTranUIT]

Thanks, I will update it soon 👍