-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Service of static redfish tree GET response with ContentType: application/xml instead of ContentType: application/json #114
Comments
Just tested the emulator using Postman and the response has Content-Type = application/json. Will look further. |
When you make the GET request, is "Accept: application/json" set in the request header? |
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. |
A search finds... Change FireFox's default Accept header to prefer JSON over XML
|
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! |
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
The text was updated successfully, but these errors were encountered: