ThreeFire1 opened a new issue, #18696:
URL: https://github.com/apache/dolphinscheduler/issues/18696

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   When testing an HTTP task on 3.4.3, I noticed that parameters added under 
HTTP Parameters are not sent when the request method is DELETE.
   
   For example, with URL /capture?existing=1 and a separate parameter jobId=42 
(type PARAMETER), the server receives:
   `DELETE /capture?existing=1`
   
   The jobId parameter is missing. Switching to GET sends it correctly. Adding 
jobId=42 directly to the URL also works with DELETE.
   
   ### What you expected to happen
   
   The server should receive both parameters:
   `DELETE /capture?existing=1&jobId=42`
   
   The [HTTP task 
docs](https://github.com/apache/dolphinscheduler/blob/043060b0587842ab2d7815048a6bc8534dad7ab3/docs/docs/en/guide/task/http.md)
 describe HTTP Parameters as GET/DELETE request parameters.
   
   ### How to reproduce
   
   1. Use a test HTTP endpoint that logs incoming requests and returns 200.
   2. Create an HTTP task with method DELETE and URL 
`http://<host>:<port>/capture?existing=1`.
   3. Add an HTTP parameter: name jobId, type PARAMETER, value 42.
   4. Save and run the workflow, then check the endpoint's log. The request 
contains existing=1 but no jobId.
   
   ### Anything else
   
   HttpTask.sendDeleteRequest() does not pass the configured query parameters 
to OkHttpUtils.delete(). The GET path passes them to OkHttpUtils.get().
   I also reproduced this in a unit test on dev commit 
043060b0587842ab2d7815048a6bc8534dad7ab3.
   
   ### Version
   
   3.4.3
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: 
[email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to