Support AWS File Path

[AonanLi]

The image path I'm using looks like this one:
"https://s3.amazonaws.com/123.com/123/123/1297/2018_04_23_3:51:11.jpg?AWSAccessKeyId=123456&Expires=123456&Signature=123456"

Wonder if we could support this kind of path.
Thanks

[adamk22]

I'm using a similar path for an image that's stored on an AWS server. If I use the path in the browser, the image displays. However, if I use the same link in photoviewer, I get a photo viewer error: the file to show is not a valid image, or could not be loaded.

Using a different (public) image seems to work just fine and the photoviewer will display correctly.

I've also tried extracting the parameters, putting it in a json object and pass it as a string to the headers option property, but without luck (I'll get the same error).

I came across this issue: #219 which states that headers aren't even applied when given. Not sure if this is the case or whether it's been fixed or not.

[rolinger]

@adamk22 @sarriaroman - I can confirm headers aren't being passed. There was a pull request back in 2019 indicating that headers were being added. But I don't think that the case. And if they are, need a callback to display errors or what headers are being passed - as of right now I can't see any of the calls coming from the app photoviewer. Right now trying to comb through apache server logs to see if I see the incoming headers that way.