Earlier quoted context omitted.
Nope you just use a POST request...
How does a legitimate user clicking on a link inside an email generate a POST request?
It loads a page which then makes a POST request to an API via JS.
Why I created scrt.link
41–43 of 43 posts
Re: Why I created scrt.link
#42Earlier quoted context omitted.
How does a legitimate user clicking on a link inside an email generate a POST request?
It loads a page which then makes a POST request to an API via JS.
Thanks again for all the feedback. Short update:
I'm using DELETE now, since it feels a bit more accurate. As a side effect, the page is way more responsive. :)
Have fun sharing secrets. C.
Re: Why I created scrt.link
#43Earlier quoted context omitted.
On a related note, I see that getting the secret is a GET request. However, since that request also deletes the secret I think it would be best if it was a POST request. This would probably also automatically fix any issue of a link preview triggering the secret deletion because I think they are designed to not execute POST requests generally speaking (but I could be wrong here).
Very good point! Thank you. I'll look into this.
Issue is resolved. Using DELETE request now, which feels a bit more accurate. Blocking crawlers is no longer needed, which also benefits page speed! Thanks again for the input. C.