You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@usergrid.apache.org by "Mike Dunker (JIRA)" <ji...@apache.org> on 2016/02/12 09:59:18 UTC

[jira] [Created] (USERGRID-1260) Asset and Accept Header changes

Mike Dunker created USERGRID-1260:
-------------------------------------

             Summary: Asset and Accept Header changes
                 Key: USERGRID-1260
                 URL: https://issues.apache.org/jira/browse/USERGRID-1260
             Project: Usergrid
          Issue Type: Story
            Reporter: Mike Dunker
            Assignee: Mike Dunker


Fixes:
1. GET entity with text/html was returning an error. Now entity retrieval returns 406 Not Acceptable if text/html is only acceptable type (must allow application/json even if text/html is preferred).
2. PUT was leaving all files in the payload of the entity -- only text/plain files should be embedded in the entity payload.
3. PUT/POST file was being allowed even on non entities. Now only PUT /collection/entity, POST /collection/entity, and POST /collection (auto-creates entity) are allowed. Others return 400 Bad Request.
4. GET of asset file streams is now locked down to GET /collection/entity. Other URL patterns return 404 Not Found.
5. For GET of asset file streams, if either the entity itself or the asset for an entity is not found, it now returns 404.
6. Accept header was not being validated for GET of asset file streams. Now an accept header that is compatible with the file type is required (otherwise returns 406 Not Acceptable).
7. Other errors in GET asset streams function were cleaned up (404 when asset not found, 500 when something goes wrong with retrieval).
8. Added tests and fixed other tests (since text/html entity requests are now locked down).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)