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

Internal Server Error from /cachegroups parameter #4703

Closed
2 of 16 tasks
dpham692 opened this issue May 19, 2020 · 0 comments · Fixed by #4721
Closed
2 of 16 tasks

Internal Server Error from /cachegroups parameter #4703

dpham692 opened this issue May 19, 2020 · 0 comments · Fixed by #4721
Labels
bug something isn't working as intended low impact affects only a small portion of a CDN, and cannot itself break one Traffic Ops related to Traffic Ops

Comments

@dpham692
Copy link
Contributor

dpham692 commented May 19, 2020

I'm submitting a ...

  • bug report
  • new feature / enhancement request
  • improvement request (usability, performance, tech debt, etc.)
  • other

Traffic Control components affected ...

  • CDN in a Box
  • Documentation
  • Grove
  • Traffic Control Client
  • Traffic Monitor
  • Traffic Ops
  • Traffic Ops ORT
  • Traffic Portal
  • Traffic Router
  • Traffic Stats
  • Traffic Vault
  • unknown

Current behavior:

When perform a GET with character type parameter query, the API will return Internal Server Error
/api/3.0/cachegroups?type=WRONG

Expected / new behavior:

Should return 400 Bad Request

Minimal reproduction of the problem with instructions:

Anything else:

@rawlinp rawlinp added bug something isn't working as intended low impact affects only a small portion of a CDN, and cannot itself break one Traffic Ops related to Traffic Ops labels May 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something isn't working as intended low impact affects only a small portion of a CDN, and cannot itself break one Traffic Ops related to Traffic Ops
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants