Timeline for REST URL taxonomy when sensitive data passed in header
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 28, 2024 at 15:03 | answer | added | VoiceOfUnreason | timeline score: 0 | |
| Oct 15, 2024 at 20:44 | comment | added | Ewan | the usual reason is that the urls are logged | |
| Oct 15, 2024 at 18:07 | comment | added | Bryn Davis | lets say it's an email. there is a requirement to be able to look-up using sensitive data. | |
| Oct 15, 2024 at 7:07 | comment | added | Ewan | its probably an email or username | |
| Oct 15, 2024 at 1:23 | comment | added | Flater | How is the public identifier of your user considered sensitive data? This sounds like an XY problem where the true source of the issue is that you're using sensitive data as a public identifier in the first place, and the solution here isn't to hide it but rather to pick a better public identifier in the first place. | |
| Oct 13, 2024 at 18:46 | review | Close votes | |||
| Oct 28, 2024 at 3:03 | |||||
| Oct 13, 2024 at 9:38 | answer | added | Ewan | timeline score: 1 | |
| Oct 13, 2024 at 9:05 | history | edited | Bryn Davis | CC BY-SA 4.0 |
edited body
|
| S Oct 13, 2024 at 9:05 | review | First questions | |||
| Oct 14, 2024 at 17:33 | |||||
| S Oct 13, 2024 at 9:05 | history | asked | Bryn Davis | CC BY-SA 4.0 |