Add support to ContentTypeParser for storing content type parameters
See original GitHub issueCurrently, ContentTypeParser
strips off any parameters to the content type, and discards them.
We should extend this class to preserve these parameters in some way in the metadata.
Examples:
application/json; charset=utf-8
application/ld+json; profile="https://www.w3.org/ns/activitystreams"
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Add support to ContentTypeParser for storing content type ...
I've got the code to extract the parameters as well as the contentType value. I would just needs some help as to under...
Read more >ContentTypeParser - Fastify
Content -Type Parser. Natively, Fastify only supports 'application/json' and 'text/plain' content types. If the content type is not one of these, ...
Read more >Header parameters: "Accept" and "Content-type" in a REST ...
In responses, a Content-Type header tells the client what the content type of the returned content actually is. Browsers will do MIME sniffing...
Read more >Handle content types - Azure Logic Apps - Microsoft Learn
Learn how to handle various content types in workflows during design time and run time in Azure Logic Apps.
Read more >content-type-parser v1.0.2 - npm.io
This package will parse the Content-Type header field into an introspectable data structure, whose parameters can be manipulated:
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 Free
Top 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
Added in #1196
The above proposal looks good to me, actually!