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

profileparameters POST request with no request body returns Internal Server Error #4428

Closed
2 of 16 tasks
ericholguin opened this issue Feb 21, 2020 · 3 comments · Fixed by #7194
Closed
2 of 16 tasks
Labels
bug something isn't working as intended good first issue first-time committers will find this easy to resolve hacktoberfest low difficulty the estimated level of effort to resolve this issue is low low impact affects only a small portion of a CDN, and cannot itself break one Traffic Ops related to Traffic Ops

Comments

@ericholguin
Copy link
Contributor

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:

Making a POST request to /profileparameters with no body in the request returns:

HTTP/1.1 500 Internal Server Error
{
    "alerts": [
        {
            "text": "Internal Server Error",
            "level": "error"
        }
    ]
}

Expected / new behavior:

Most endpoints return:

HTTP/1.1 400 Bad Request 
{
    "alerts": [
        {
            "text": "EOF",
            "level": "error"
        }
    ]
}

Minimal reproduction of the problem with instructions:

Anything else:

@ocket8888
Copy link
Contributor

Is that a regression, or did Perl panic too?

@ocket8888 ocket8888 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 Feb 21, 2020
@ericholguin
Copy link
Contributor Author

Perl returned:

HTTP/1.1 400 Bad Request
{
    "alerts": [
        {
            "level": "error",
            "text": "parameters must be in JSON format."
        }
    ]
}

@ocket8888 ocket8888 added the regression bug a bug in existing functionality introduced by a new version label Feb 21, 2020
@mitchell852 mitchell852 removed the regression bug a bug in existing functionality introduced by a new version label Apr 20, 2020
@mitchell852 mitchell852 added good first issue first-time committers will find this easy to resolve hacktoberfest labels Aug 18, 2020
@mitchell852 mitchell852 added the low difficulty the estimated level of effort to resolve this issue is low label Dec 7, 2021
@ocket8888
Copy link
Contributor

This is also caused syntactically invalid bodies e.g. [, {, and any valid JSON that isn't an object or array e.g. "string", null

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 good first issue first-time committers will find this easy to resolve hacktoberfest low difficulty the estimated level of effort to resolve this issue is low 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.

3 participants