Content-Type is missing for Post request header
Opened this issue · 0 comments
Description
Running RESTler on Fabric Eventstream service. The post request failed with 500. I debug our code, the real exception was
"The request contains an entity body but no Content-Type header. The inferred media type 'application/octet-stream' is not supported for this resource." which means Content-Type is null/missing in the request header.
I've specified the Content-Type in my swagger file:
+++ Combination 1 +++:
Request sequence:
> POST /webapi/capacities/98C777F0-0CF9-411C-873B-CC7EB7A6EC67/workloads/ES/ESService/direct/v2/workspaces/e3aab0cc-2dfe-4885-8f18-38da3ab077c9/artifacts/f0f646aa-a617-47b5-acb8-254a824de2c7/saveTopology HTTP/1.1\r\nAccept: application/json\r\nHost: hc0104.edogmwcrelay.pbidedicated.windows-int.net\r\nAUTHORIZATION TOKEN\r\n\r\n{\n "topology":"fuzzstring",\n "properties":\n {\n "dataSources":\n [\n {\n "id":"4d2bc7f9-fd93-46b0-9c36-4d9508e17bbc",\n "name":"fuzzstring",\n "direction":"Unknown",\n "type":"Unknown",\n "properties":\n {\n "upstreamName":"fuzzstring"\n }\n ,\n "startOnCreated":true,\n "startOption":\n {\n "startType":"Unknown",\n "customStartTime":"2019-06-26T20:20:39+00:00"\n }\n }\n ],\n "streams":\n [\n {\n "id":"be300a78-2cdc-44d2-891a-2d516a5fc0bb",\n "name":"fuzzstring",\n "type":"DefaultStream",\n "properties":\n {\n "upstreamName":"fuzzstring",\n "transformation":"fuzzstring",\n "inputSerialization":\n {\n "type":"Unknown",\n "properties":\n { "fuzz": false }\n }\n }\n }\n ],\n "eventLinks":\n [\n {\n "id":"6f63363b-24b8-4c36-a1f4-6b89b1e1b5ab",\n "systemTopicResourceId":"fuzzstring",\n "azureResourceId":"fuzzstring",\n "principalId":"a664186e-e09e-485e-87e8-305c2f3d940e",\n "filterInfo":\n {\n "includedEventTypes":\n [\n "fuzzstring"\n ],\n "filters":\n [\n {\n "values":\n [\n "fuzzstring"\n ],\n "operatorType":"fuzzstring",\n "key":"fuzzstring"\n }\n ]\n }\n }\n ]\n }\n }\r\n
< HTTP/1.1 500 Internal Server Error\r\nDate: Wed, 23 Oct 2024 13:35:26 GMT\r\nContent-Type: application/xml; charset=utf-8\r\nTransfer-Encoding: chunked\r\nConnection: keep-alive\r\nVia: 1.1 edogmwcrelay.servicebus.windows.net\r\nStrict-Transport-Security: max-age=31536000\r\nx-ms-routing-hint: host001_es-001\r\nx-ms-root-activity-id: 19c4f543-0924-4da5-a1bc-134a3ee49a73\r\nx-ms-current-utc-date: 10/23/2024 1:35:20 PM\r\nx-azure-ref: 20241023T133520Z-155bbb994fdffg5jkrp4z0ansc00000007f0000000019xy0\r\nX-Cache: CONFIG_NOCACHE\r\n\r\n3ae\r\n{"code":"UnKnown","subCode":0,"message":"An internal error occurred.","timeStamp":"2024-10-23T13:35:25.8427801Z","httpStatusCode":500,"hresult":-2147467259,"details":[{"code":"RootActivityId","message":"19c4f543-0924-4da5-a1bc-134a3ee49a73"},{"code":"PowerBIApiErrorResponse","message":"{"error":{"code":"UnKnown","message":"Processing of the HTTP request resulted in an exception. Please see the HTTP response returned by the 'Response' property of this exception for details.","pbi.error":{"code":"UnKnown","details":[{"code":"UnKnown","detail":{"type":1,"value":"Processing of the HTTP request resulted in an exception. Please see the HTTP response returned by the 'Response' property of this exception for details."}}]}}}"},{"code":"Param1","message":"Processing of the HTTP request resulted in an exception. Please see the HTTP response returned by the 'Response' property of this exception for details."}]}\r\n0\r\n\r\n
Steps to reproduce
Expected results
No response
Actual results
No response
Environment details
No response