mirror of
https://github.com/BobbyWibowo/lolisafe.git
synced 2024-12-14 16:36:21 +00:00
40dd662976
I wasn't aware ShareX wouldn't do a basic GET request to the delete URL, but would instead open your browser to it. Unfortunately, due to the structure of lolisafe auth setting token through HTTP header, which had always been done by JS as it has to get the value from local storage, just visiting the API from browser will merely respond with "No token provided". We'd need cookie-based auth, which I do not want to add. The old me that added deletion API long ago might have been aware of this fact, but the me of a few hours ago already forgot.. I'll give this further thoughts at a later date, as ShareX isn't really a priority to me. Bumped v1 version string and rebuilt client assets. |
||
---|---|---|
.. | ||
render.js | ||
render.js.map | ||
utils.js | ||
utils.js.map |