Images interoperability issue between hosted parse and S3 hosting

[vickyteke]

Check out this issue for an ideal bug report. The closer your issue report is to that one, the more likely we are to be able to help, and the more likely we will be to fix the issue quickly!

For implementation related questions or technical support, please refer to the Stack Overflow and Server Fault communities.

Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!

• You've met the prerequisites.
• You're running the latest version of Parse Server.
• You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Environment Setup

1. Set up S3 to host your app's image.
2. Run the latest parse-server.
3. Create a web app pointing to the parse-server.
4. Store images using PFFile and parse-server.

The images could be stored in a class in two ways
A. as a field in the class
B. in an array field in the class.

If PFFile is stored in a field in a class, it only contains the image name, but if it is stored as an array in a field, then it contains the url also.

Interop Problem 1.
The users who are using an app that is still pointing to hosted parse api server, are not able to see the S3 image for option A above. This is because hosted parse returns the url prefixed with files.parsetfss.com + <name_of_the_image.jpeg>. However, they are able to see the images which are stored in an array field as it contains the full url of the images (option B above).

Interop Problem 2.
The users who are on the app pointing to parse-server are not able to see the images stored as option A by hosted parse because not all the images start with the name "tfss-". Parse-server returns the constructed url as if it was stored in S3. Users are able to see the images stored as in option B.

[flovilmart]

Closing as duplicate of #8