This is because for the API a value of 0 != Null.
If you want to remove the TipMix header, you will need to set the value to null using either ARM Client and or Resource Explorer
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
After having tried the test-in-production feature with 5% in staging slot, I turned back to 100% production.
To my surprise all responses still get the TipMix and x-ms-routing-name cookies set in the reponse headers.
Is there a way of turning off this feature or remove the cookie headers?
We have IoT products that get problems when the header section of the response gets too long.
Optimally we would like to control the raw HTTP response in detail without the Azure infrastructure adding extra headers.
This is because for the API a value of 0 != Null.
If you want to remove the TipMix header, you will need to set the value to null using either ARM Client and or Resource Explorer
Could you please tell us where in Resource Explorer we have to set the value and for which attribute?