Author Message
Teng_08
Joined: Mar 18, 2024
Messages: 2
Offline
Hi,

We are having issue and getting response for API in html format instead of json format.

Web Service Reply <- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Bad Request</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Bad Request - Invalid Header</h2>
<hr><p>HTTP Error 400. The request has an invalid header name.</p>
</BODY></HTML>

The API endpoint is asking for the Azure Ref ID to troubleshoot on their side. But the Ref ID is in response header and is not visible in the trace logs. Is there a way to get the API header details from trace logs?
massimo__croci
Joined: Jan 31, 2020
Messages: 518
Offline
Hi.

What Ref ID are you referring to ?

Here https://learn.microsoft.com/en-us/azure/frontdoor/front-door-diagnostics?pivots=front-door-standard-premium

it states

"Access logs, health probe logs, and WAF logs aren't enabled by default. To enable and store your diagnostic logs, see Configure Azure Front Door logs. Activity log entries are collected by default, and you can view them in the Azure portal.

Access log
Information about every request is logged into the access log. Each access log entry contains the information listed in the following table.

Property
TrackingReference

Description
The unique reference string that identifies a request served by Azure Front Door. The tracking reference is sent to the client and to the origin by using the X-Azure-Ref headers. Use the tracking reference when searching for a specific request in the access or WAF logs.


Teng_08
Joined: Mar 18, 2024
Messages: 2
Offline
We are trying to get the Ref ID from the response header in Orchestration Designer logs. We don't see the header details in the OD trace logs. We see the Ref ID in response header if we test API connection using SOAP UI
Go to:   
Mobile view