I'm happy to hear that folder name and file name is on the near roadmap for completion. I do see that you catch up very quicklyġ. You guys are awesome!! Thanks for all your hard work. Can you go to the console (right-click -> inspect element) to see if there is anything abnormal (that is error in the Console or different than 200 status code in any of the network requests). It looks like it has failed on your side. In the background JavaScript tries to fetch the asset and replaces the one on the screen with decrypted version. What it does it tries to load the encrypted asset as usual, but it's not aware per se if an asset is encrypted. The encrypted share link has the master key at the end after the # character and looks like this: For instance we could combine this with a link shortener, so there is single link that doesn't change, but under the hood we would regenerate the destination link as needed. We're researching how to overcome this limitation. The sharing functionality is based on S3 presign URLs, their limitation is that the signature can't be valid longer than 7 days, so every 7 days new link would have to be generated. We're making further research to understand standards or well established implementation in that area, so we can stay compatible. Likely the endpoint without scheme will default to https, where as IP addr will default to http.įilename encryption is on our Roadmap and we have a working prototype already. Hi you're right if no scheme (https/http) was provided it defaulted to HTTP.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |