Timeline for How to best protect a public API from unwanted requests
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 2, 2023 at 11:51 | vote | accept | user8758206 | ||
| Apr 1, 2023 at 8:09 | comment | added | user8758206 | it would be interesting to hear of defence ideas against this. Wouldn't IP throttling prevent this (unless the attacker could somehow keep changing their IP)? | |
| Mar 31, 2023 at 14:37 | comment | added | S.D. | And cannot another such user, simply write a script to load the website in a large number of simulated browsers and do fake web page interactions to generate the same amount of junk data ? | |
| Mar 31, 2023 at 8:51 | review | Close votes | |||
| Apr 5, 2023 at 3:04 | |||||
| Mar 31, 2023 at 8:30 | comment | added | pjc50 | Does this answer your question? The best way of preventing unauthorised API use and reducing costs of declining API requests | |
| Mar 31, 2023 at 7:42 | answer | added | DavidT | timeline score: 1 | |
| Mar 30, 2023 at 22:07 | history | edited | user8758206 | CC BY-SA 4.0 | added 189 characters in body |
| Mar 30, 2023 at 22:02 | answer | added | Philip Kendall | timeline score: 3 | |
| Mar 30, 2023 at 21:58 | history | edited | user8758206 | CC BY-SA 4.0 | added 47 characters in body |
| Mar 30, 2023 at 21:53 | history | edited | user8758206 | CC BY-SA 4.0 | added 47 characters in body |
| S Mar 30, 2023 at 21:48 | review | First questions | |||
| Mar 31, 2023 at 7:50 | |||||
| S Mar 30, 2023 at 21:48 | history | asked | user8758206 | CC BY-SA 4.0 |