This sounds a little counterintuitive, because the header is a way to get around certain complex values registering as formats in the URL; but fortunately with #60 the developer can specify a regex for their complex tokens, and this should be less of an issue.
The monkey wrench is that if you're just making a vanilla request in the browser for "foo.json" the browser sends an Accept header of text/html. So for that reason, we should give url format/extension precedence over the Accept header because the user entering "foo.json" clearly has a better idea of what they want than the browser, which is just guessing.
For documentation: format specification as ".format" should be un-deprecated with this change!
documented here: https://github.com/atuttle/Taffy/wiki/So-you-want-to:-Support-returning-multiple-formats
Code changes for #92 - makes url extension take precedence over accep…
git-svn-id: https://github.com/wolfnet/Taffy.git/branches/develop@359 a9f385df-67b6-ee62-c877-ce57b7db7bff