[
https://issues.apache.org/jira/browse/USERGRID-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Shelley updated USERGRID-982:
-------------------------------------
Description:
1. The Accept header should be inferred from the filename extension if it exists
2. Assets should support retrieval by passing either the original filename or
"asset" if it is unknown. Any extension should also be ignored (the
content-type header will be set to the original asset)
E.g. the following should all work:
GET /pictures/cat/original_file_name
GET /pictures/cat/original_file_name.jpg
GET /pictures/cat/asset
GET /pictures/cat/asset.jpg
3. DELETE/PUT should also be supported for the /asset path as well, e.g.:
DELETE /pictures/cat/original_file_name
DELETE /pictures/cat/asset
was:The Accept header should be inferred from the filename extension if it
exists.
Summary: Support for /filename.ext for Binary Assets (was: Support for
filename+extension for Binary Assets)
> Support for /filename.ext for Binary Assets
> -------------------------------------------
>
> Key: USERGRID-982
> URL: https://issues.apache.org/jira/browse/USERGRID-982
> Project: Usergrid
> Issue Type: Story
> Reporter: Jeffrey
>
> 1. The Accept header should be inferred from the filename extension if it
> exists
> 2. Assets should support retrieval by passing either the original filename or
> "asset" if it is unknown. Any extension should also be ignored (the
> content-type header will be set to the original asset)
> E.g. the following should all work:
> GET /pictures/cat/original_file_name
> GET /pictures/cat/original_file_name.jpg
> GET /pictures/cat/asset
> GET /pictures/cat/asset.jpg
> 3. DELETE/PUT should also be supported for the /asset path as well, e.g.:
> DELETE /pictures/cat/original_file_name
> DELETE /pictures/cat/asset
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
