Service of static redfish tree GET response with ContentType: application/xml instead of ContentType: application/json

DMTF / Redfish-Interface-Emulator

The Redfish Interface Emulator can emulate a Redfish-based interface statically (GET) or dynamically (POST, PATCH, DELETE)

Other

59 stars 24 forks source link

Service of static redfish tree GET response with ContentType: application/xml instead of ContentType: application/json #114

Closed JohnMayfieldHPE closed 3 months ago

JohnMayfieldHPE commented 1 year ago

Running a vanilla copy of v1.1.8 on a static redfish mockup starts the service and finds the redfish tree in the static directory OK, however when doing a GET on the service_root (or any other URI within the static tree) returns the content with the response header value ContentType set to application/xml instead of application/json. This causes the client browser to attempt to parse the response as XML and returns errors to the user: XML Parsing Error: not well-formed

jcleung5549 commented 1 year ago

Just tested the emulator using Postman and the response has Content-Type = application/json. Will look further.

jcleung5549 commented 1 year ago

When you make the GET request, is "Accept: application/json" set in the request header?

JohnMayfieldHPE commented 1 year ago

I was only using firefox for initiating the GET request, not postman. I'm not sure how to tell Firefox to explicitly set Accept: application/json in the headers.

jcleung5549 commented 1 year ago

A search finds...

Change FireFox's default Accept header to prefer JSON over XML

In the address bar in FireFox, type “about:config”.
Click the “I promise” button.
In the search bar type “network. http. ...
Double-click the setting.
In the comma-separated list add a new value of “application/json” (without the quotes)

JohnMayfieldHPE commented 1 year ago

I think that is my problem, I didn't have the acceptable header content types in the request from firefox. I'll adjust and most likely close this issue. Thank you for the help John!