Incorrect parsing of content type application/hal+json
See original GitHub issueHi, we switched to superagent version 1.6.1
we have backend-response content-type: "application/hal+json"
according to some previous issues the parser should be updated to support +json types but the npm ships superagent without the right parser.
Issue Analytics
- State:
- Created 8 years ago
- Reactions:1
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Incorrect parsing of content type application/hal+json #816
Hi, we switched to superagent version 1.6.1 we have backend-response content-type: "application/hal+json" according to some previous issues ...
Read more >Incorrect parsing of content type application/hal+json
Hi, we switched to superagent version 1.6.1. we have backend-response content-type: "application/hal+json" according to some previous issues ...
Read more >The application/problem+json Content-Type - SymfonyCasts
So the json part tells us how to parse the document. The problem part give us a hint on how to find out...
Read more >java - Cannot do HAL+JSON Level 3 RESTful API with Spring ...
This is the reason, why the media type is called application/hal+json . It basically says it's the HAL style/semantics in the JSON format....
Read more >Response does not have a content-type header
On the request side, I've never seen a Content-Type that is a comma separated list. Is that legal? Do you mean for "application/json...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This worked for me (FF-47)
This has been fixed around version 1.8