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

API-DOC through web UI, POST and PUT use default Xml may fail, have to use Json #603

Open
3 tasks
alin2k opened this issue Nov 2, 2017 · 3 comments
Open
3 tasks

Comments

@alin2k
Copy link

alin2k commented Nov 2, 2017

Description

OSC ipaddr:8090/api-doc manually test API POST e.g. POST /api/server/v1/virtualizationConnectors/{vcId}/serviceFunctionChain got "bad request" by default using default content-type "application/xml" form, has to select "application/json" to make it work.

Expected Behavior

API should accept both format xml/json when do POST or PUT

Actual Behavior

Only accept Json format (default is Xml) to POST or PUT, Xml got error "Bad Request"

Steps to Reproduce

1)https://10.3.240.156:8090/api-doc/ ->Operations for Virtualization Connectors
2)POST /api/server/v1/virtualizationConnectors/{vcId}/serviceFunctionChain and enter white entries value of "vcId" and "body" for name and virtualSystemIds
3)Click "Try It Out!" and response got "bad request"
4)Select from Xml to Jason, POST works and got response 200

Additional Information: log attached:

xmlPostBadReqLog800.txt

Environment

  • OSC Version/Build: v0.8 build#1
  • Cloud Provider Info:
  • Plugin Info:
  • Other:

Status

  • Reproduced
  • In Progress
  • Validated => Verified in Version/Build:
@arvindn05
Copy link
Member

@alin2k what does "enter white entries value" mean?
description is unclear, please add logs better description and screenshots if applicable. Please have one of the other QA members review this as well.

@sudhirappaji
Copy link
Member

@alin2k , please provide info and if we don't receive information in 2 weeks we are going to close the issue.

@alin2k
Copy link
Author

alin2k commented Nov 29, 2017

Steps modified. log attached when it's a "bad request" in POST.
Basically Dev knows API POST has to use Jason instead Xml which is default in API web page

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants