Open
Description
When I have an active rule on an override on a domain, even if it did not match the HTTP request other than being on the same domain, the response application/json with value true, which is valid json text,
is parsed as
When disabling overrides, it is back to
I checked, the response is pure ASCII, seems to be nothing fuzzy about it, but it gets wrongly presented in the tools and parsing in the application fails, so somehow the response has been tampered with.

* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
< HTTP/2 200
< date: Wed, 19 Jun 2024 09:22:59 GMT
< content-type: application/json; charset=utf-8
< access-control-allow-credentials: true
< access-control-allow-origin: https://xxxxxxxxxxx
< vary: Origin
< strict-transport-security: max-age=2592000
< request-context: appId=cid-v1:xxxxxxxxxxxxxxxxx
< api-supported-versions: 1.0-internal, 1.0
< x-powered-by: ASP.NET
< x-azure-ref: xxxxxxxxxxxxxxxxxxxxxxxxxxx
< x-cache: CONFIG_NOCACHE
<
* Connection #0 to host xxxxx left intact
true⏎