Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GET /api/1.3/cdns returns wrong response code and response format when unauthorized or forbidden #1829

Closed
mitchell852 opened this issue Jan 31, 2018 · 0 comments · Fixed by #1835
Labels
high impact impacts the basic function, deployment, or operation of a CDN regression bug a bug in existing functionality introduced by a new version
Milestone

Comments

@mitchell852
Copy link
Member

If you try to access GET /api/1.3/cdns without being logged in (i.e. no valid cookie) the response should look like this:

401 Unauthorized

{
alerts: [
{
level: "error",
text: "Unauthorized, please log in."
}
]
}

If you are authenticated (your login cookie is valid) but your user doesn't have the proper priv level, the response should look like this:

403 Forbidden

{
alerts: [
{
level: "error",
text: "Forbidden."
}
]
}

@mitchell852 mitchell852 added bug something isn't working as intended Traffic Ops API (golang) regression bug a bug in existing functionality introduced by a new version labels Jan 31, 2018
@mitchell852 mitchell852 added this to the 2.2.0 milestone Jan 31, 2018
@mitchell852 mitchell852 added this to To Do in TO API Golang Rewrite via automation Jan 31, 2018
TO API Golang Rewrite automation moved this from To Do to Done Feb 1, 2018
@mitchell852 mitchell852 removed the bug something isn't working as intended label Aug 28, 2020
@mitchell852 mitchell852 added the high impact impacts the basic function, deployment, or operation of a CDN label Nov 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
high impact impacts the basic function, deployment, or operation of a CDN regression bug a bug in existing functionality introduced by a new version
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

1 participant