-
Should be a configurable middleware that handles content negotiation as per [RFC 7231](https://tools.ietf.org/html/rfc7231#section-5.3)
-
Currently according to [route](https://github.com/mozilla/makedrive#routes), the content type is hardcoded in the path root. Is there a reason to have chosen that design over an extension? It also mak…
-
Any book about REST APIs should have a section on content negotiation including popular formats like
_Document formats_
JSON API
HATEOAS
_And things like_
Localisation/multi-lingual APIs
Con…
-
Got this request from today from one of the feature teams:
> hi, we are thinking about a simple CSV data export. do you think this would
> be appropriate to add to our data API endpoints as a differ…
-
What do you think of the idea to add a new subsection reflecting the new CN style [Request Content Negotiation](https://www.rfc-editor.org/rfc/rfc9110.html#name-request-content-negotiation) introduced…
-
Content negotiation is not (currently!) part of routing in Tide, but we should decide whether we want that to change, and if not, how to make it easy for an endpoint to internally perform content nego…
-
When Denali responds to a request, it runs through the responder setup here (https://github.com/denali-js/denali/blob/master/lib/runtime/action.js#L251-L277), allowing data to be formatted differently…
-
When using `createMiddleware` or `withArcjet` via `@arcjet/next`, the handlers should use content negotiation to figure out what format to send back (json/html/etc).
-
As both Google Chrome and Imagick support AVIF, it would be nice to have this format supported.
If we look at how WebP support was added in this bundle (see https://github.com/liip/LiipImagineBundl…
-
Hello, I have noticed that `http://schema.org` does not resolve to a machine-readable format:
```
curl -H "Accept:application/ld+json" -L http://schema.org/
```
Returns HTML. (Also tried with `a…