OpenAPI Extension: Action Returns Unexpected Response?
Open
Nobody has claimed this yet.
add-on
Component-API
in:openapi
Usability
- Dominant language
- Java
- Stars
- 15.8k
- Forks
- 2.6k
- Avg merge
- 13h 16m
- Merged PRs (30d)
- 17
Description
Steps to reproduce:
- Configure ZAP UI to be accessible as a local proxy.
- Browse to
http://localhost/UI/openapi/action/importUrl/and provide a valid URL. - Open the network debugger of your browser's development tools.
- Press "importUrl".
- Now
{"importUrl":[]}is the response. Instead something with "OK" is expected as all the other options do it.
Also in case of an import error I would expect something different than a 200 status (but actually there is no distinction).
Thank you for looking into it. :)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the OpenAPI action at /UI/openapi/action/importUrl/ and compare its response with the other OpenAPI actions. Check the response for a successful import and for an import error; done means success is distinguishable from failure and the HTTP status and response body match the expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, openapi
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100