Wildcard content types support
See original GitHub issueUsing content types *.*
does not work atm when specified in requestBody.
requestBody:
content:
"*/*":
schema:
When route is reached the validation returns unsupported media type
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Is '*' a valid wildcard for a content type according to HTTP spec?
It explicitly mentions supported media types like "n/m" where m could be * or n and m could be *, but only *...
Read more >Examples of wildcard characters - Microsoft Support
Wildcards are special characters that can stand in for unknown characters in a text value and are handy for locating multiple items with...
Read more >Are wildcard media types supported in content? #1290 - GitHub
If wildcard types are supported in content , how does this work? Do more specific types have preference over wildcard ones, e.g. image/png ......
Read more >Supported Wildcards for NDMP - Commvault Documentation
When you use wildcards to specify subclient content, the content path appears in italics. You can use more than one type of wildcard...
Read more >Security/CSP/Specification - MozillaWiki
Content Security Policy is intended to help web designers or server ... It helps mitigate and detect types of attacks such as XSS...
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
Yeah sure I’ll have a go this or next week and will PR it.
@cdimascio
I’ve put up a pull request to add @jordandobrev! 🎉