[RTFACT-11878] Some REST resources return a Content-Type that does not match the documentation Created: 08/Jul/16 Updated: 14/Nov/17
|Project:||Artifactory Binary Repository|
|Affects Version/s:||4.7.7, 4.9.0|
|Reporter:||Arturo Aparicio||Assignee:||Gidi Shabat|
Some REST resources return a Content-Type that does not match the documentation.
For example, according to the documentation, this REST call should return application/vnd.org.jfrog.artifactory.security.PermissionTargets+json but instead the Content-Type is application/vnd.org.jfrog.artifactory.security.Users+json. Performing an OPTIONS call on that resource shows that it may return various Content-Types, including both of the aforementioned types:
In fact, if the user provides the header "Accept: application/vnd.org.jfrog.artifactory.security.PermissionTargets+json", the correct Content-Type will be returned. Still the call should default to the correct Content-Type or the documentation should be updated for accuracy.
1) api/security/permissions - need to produce application/vnd.org.jfrog.artifactory.security.PermissionTargets+json and NOT application/vnd.org.jfrog.artifactory.security.Users+json
|Comment by Andrei Komarov [ 26/Jul/16 ]|
The REST API for virtual repository update does not work with the specific JSON object required header (instead it works with the application/json):
|Comment by Shlomi Kriheli [ 13/Nov/16 ]|
I fixed the documentation per Arturo's and Andrei's comments.
2) api/security/groups - need to produce application/vnd.org.jfrog.artifactory.security.Groups+json and NOT application/vnd.org.jfrog.artifactory.security.Users+json
Moving to RnD to fix.