-
A vital part of this application is content creation and moderation by the community.
* Content has to be negotiated, e.g. name and brand of product (doesn't normally change), which stores carry a pr…
-
The current implementation of `EntitiesController` is wired up to a single `MetadataService` from which it queries for rendered metadata. Different presentations of this are made by the view, either `…
-
> 4.1: “MUST send content distribution requests with a matching content type of the topic URL”
Maybe you can make a short comment about content negotiation here, since that question popped up immed…
-
To accommodate diverse client preferences, I propose introducing content negotiation. This feature allows clients to request their preferred content format (e.g., JSON, XML, HTML) via the Accept heade…
-
The scenario is using content negotiation on a server to retrieve from a variety of multi-lingual XML docs which all use a common PI / XSL, which itself uses other included XSL documents, which themse…
-
Following up on recent PRs, figured I would open an Issue for now where we can kick some ideas around on the topic of content negotiation.
A few quick thoughts to kick things off. I would characte…
-
It would be nice if the content negotiation in Strata provided a way to get an ordered list of the media types a client accepts based on q values in the Accept header. For an example of a module that …
-
Currently the app is explicitly returning JSON, but might be worth considering using [Nancy's content negotiation](https://github.com/NancyFx/Nancy/wiki/Content-Negotiation) to allow other types. This…
-
I think it is harmful to have well known urls with different file type terminations (".txt, .json...").
This means bots will have to guess... and try each and every posssibility....
Better would …
-
Originally reported by: **Anonymous**
---
CherryPy doesn't (usually) respect the server preferences when it does
Accept/Content-Type negotiation.
For example, suppose Firefox sends the header:
A…
ghost updated
8 years ago