e9f5067653
They currently throw a Internal Server Error when you use them without a token. Now they correctly return a `token is required` error. This is no security issue. If you use this endpoints with a token that don't have the correct permission, you get the correct error. This is not affected by this PR. |
||
---|---|---|
.. | ||
actions | ||
packages | ||
v1 |