Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Better mechanism for content negotiation #157
It would be great to have a configurable and client-driven fallback mechanism for template resolution; for example, if there's both
Content negotiation is based on a hard-coded priority system that's universal to all templates, and disregards the client's request.
Very useful for supporting more dynamism in templates and more user-friendly feed presentation and so on.
Thoughts: have some sort of configurable mapping (ideally on a per-category and/or per-template basis) that sets the content-type for each extension, and also a default q-value for use with the
This mapping file could also be where we can configure other headers for the response, such as cache-control or content-type, rather than continuing to use the crappy hard-coded mapping in