[ https://jira.fiware.org/browse/HELP-9038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fernando Lopez updated HELP-9038: --------------------------------- Description: Created question in FIWARE Q/A platform on 09-03-2016 at 14:03 {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/35893261/fiware-object-storage-ge-different-type-of-responses-obtained-when-downloading +Question:+ FIWARE object storage GE: Different type of responses obtained when downloading an image object +Description:+ I can effectively make use of all operations available for Object Storage on my FIWARE account. Nonetheless I have identified a strange behaviour when downloading objects from a container. Please find below the procedure to reproduce that strange behaviour: I upload two objects ("gonzo.png" and "elmo.png") to the container "photos" 1.1. First, by means of cloud UI (https://cloud.lab.fiware.org/#objectstorage/containers/) I manually upload the object "gonzo.png" 1.2. Later, by following the instructions from Object Storage GE programmer's guide I programmatically (or with the help of standalone Rest Client) upload the object "elmo.png" I download the objects from the container "photos" 2.1 First, by following the instructions from Object Storage GE programmer's guide I successfully download object "gonzo.png". The webservice response body is the binary content of such object. 2.2. Later, by following same instructions as in step 2.1 I try to download the object "elmo.png". Now the webservice response body is a json with metadata and the binary content of the object. What can I do receive a standard response body for both objects? Either binary or either json. Why do I get a different response if the object is originally uploaded via Cloud UI or via external tool (program or rest client) ? As in Download blob from fiware object-storage I have already tried to set the header response_type: text and the behaviour is the same. was: Created question in FIWARE Q/A platform on 09-03-2016 at 14:03 {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/35893261/fiware-object-storage-ge-different-type-of-responses-obtained-when-downloading +Question:+ FIWARE object storage GE: Different type of responses obtained when downloading an image object +Description:+ I can effectively make use of all operations available for Object Storage on my FIWARE account. Nonetheless I have identified a strange behaviour when downloading objects from a container. Please find below the procedure to reproduce that strange behaviour: I upload two objects ("gonzo.png" and "elmo.png") to the container "photos" 1.1. First, by means of cloud UI (https://cloud.lab.fiware.org/#objectstorage/containers/) I manually upload the object "gonzo.png" 1.2. Later, by following the instructions from Object Storage GE programmer's guide I programmatically (or with the help of standalone Rest Client) upload the object "elmo.png" I download the objects from the container "photos" 2.1 First, by following the instructions from Object Storage GE programmer's guide I successfully download object "gonzo.png". The webservice response body is the binary content of such object. 2.2. Later, by following same instructions as in step 2.1 I try to download the object "elmo.png". Now the webservice response body is a json with metadata and the binary content of the object. What can I do receive a standard response body for both objects? Either binary or either json. Why do I get a different response if the object is originally uploaded via Cloud UI or via external tool (program or rest client) ? As in Download blob from fiware object-storage I have already tried to set the header response_type: text and the behaviour is the same. HD-Enabler: Object Storage > [fiware-stackoverflow] FIWARE object storage GE: Different type of responses obtained when downloading an image object > ---------------------------------------------------------------------------------------------------------------------- > > Key: HELP-9038 > URL: https://jira.fiware.org/browse/HELP-9038 > Project: Help-Desk > Issue Type: Monitor > Components: FIWARE-TECH-HELP > Reporter: Backlog Manager > Labels: fiware, object, storage > > Created question in FIWARE Q/A platform on 09-03-2016 at 14:03 > {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/35893261/fiware-object-storage-ge-different-type-of-responses-obtained-when-downloading > +Question:+ > FIWARE object storage GE: Different type of responses obtained when downloading an image object > +Description:+ > I can effectively make use of all operations available for Object Storage on my FIWARE account. > Nonetheless I have identified a strange behaviour when downloading objects from a container. > Please find below the procedure to reproduce that strange behaviour: > I upload two objects ("gonzo.png" and "elmo.png") to the container "photos" > 1.1. First, by means of cloud UI (https://cloud.lab.fiware.org/#objectstorage/containers/) I manually upload the object "gonzo.png" > 1.2. Later, by following the instructions from Object Storage GE programmer's guide I programmatically (or with the help of standalone Rest Client) upload the object "elmo.png" > I download the objects from the container "photos" > 2.1 First, by following the instructions from Object Storage GE programmer's guide I successfully download object "gonzo.png". The webservice response body is the binary content of such object. > 2.2. Later, by following same instructions as in step 2.1 I try to download the object "elmo.png". Now the webservice response body is a json with metadata and the binary content of the object. > What can I do receive a standard response body for both objects? Either binary or either json. > Why do I get a different response if the object is originally uploaded via Cloud UI or via external tool (program or rest client) ? > As in Download blob from fiware object-storage I have already tried to set the header response_type: text and the behaviour is the same. -- This message was sent by Atlassian JIRA (v6.4.1#64016)
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy