@AZ_Ferran Rubio Llovich Welcome to Microsoft Q&A Forum, Thank you for posting your query here!
I understand that the OCP-Apim-Trace-Location
response header is present even when the Allow Tracing option is disabled for that subscription.
I am unable to reproduce this issue at my end. This issue requires some isolation.
- Could you please check if the Tracing is enabled at the
Product
level ?
- Could you please try creating a new subscription (with AllowTracing Disabled) and associate it with a product / API and check if the issue happens on that too?
- Could you try creating a new API altogether and try this newly created subscription key and check if this issue occurs on that?
- Could you please try with
Ocp-Apim-Trace
toFalse
and confirm if the Trace Location response is still returned? Then send subsequent requests withOcp-Apim-Trace
asTrue
and validate again. - Please confirm if there aren't any caching policies configured for that API.
Awaiting your reply.