You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 29, 2020. It is now read-only.
According to the WC3 Specifictations the Server should try to satisfy accept headers in order. Currently the order of the content-types in the Accept header is not respected.
So when I send a request with an Accept header like this: application/xml, application/json it should first try to return a xml and then a json model. When I do application/json, application/xml it should be the other way around.
The AcceptableViewModelSelector controller plugin does not seem to respect the order in which content types are requested.
I reported this issue here inside Apigility module but it turned out the behavior is caused by the Zend\Mvc\Controller\Plugin\AcceptableViewModelSelector controller plugin.
The text was updated successfully, but these errors were encountered:
According to the WC3 Specifictations the Server should try to satisfy accept headers in order. Currently the order of the content-types in the
Accept
header is not respected.So when I send a request with an
Accept
header like this:application/xml, application/json
it should first try to return axml
and then ajson
model. When I doapplication/json, application/xml
it should be the other way around.The
AcceptableViewModelSelector
controller plugin does not seem to respect the order in which content types are requested.I reported this issue here inside Apigility module but it turned out the behavior is caused by the
Zend\Mvc\Controller\Plugin\AcceptableViewModelSelector
controller plugin.The text was updated successfully, but these errors were encountered: