When consuming APIs you often want JSON in successful scenario. Which means, if you also have JSON in unsuccessful scenario it’s a bit more uniform, because you don’t have to deal with JSON in one case and plaintext response in other. Also, it sometimes can be useful to have additional details there like server’s stacktrace or some identifiers that help troubleshoot complex issues.
I got 401 from lemmy.world with the following response payload:
{
"success": false,
"error": {
"code": 403,
"message": "Posting & Uploading blocked from VPN/Tor"
}
}
PS: yeah, I know it says it’s 403 in payload, but in response it’s 401
Yes, this is response payload it gives when hitting “Reply” or “Post” from certain VPNs:
{
"success": false,
"error": {
"code": 403,
"message": "Posting & Uploading blocked from VPN/Tor"
}
}
I also use Proton VPN. Most issues were with DE servers I tried, multiple DE servers (like DE#526) didn’t work for me, but some others seem to be working. I also tried some other countries and they were working.
Sorry for a bit of off-topic, but for a note taking app I suggest checking out Amplenote (there is a free plan for browser and mobile apps). I discovered it recently and it’s quite a life changer for me. Proper tag system for notes is a killer feature.
It’s ok for internal admin panels and their backends as there are no security concerns in this case.