For PUT/PATCH requests, the body is in param PUTDATA/PATCHDATA #1656
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bschmalhofer
approved these changes
Mar 10, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If you import the "standard" GenericTicketConnectorREST.yml file and want to update a ticket, one has to use the PATCH HTTP method to send data. The data is in the body, but without this change nothing happens as the HTTP::REST transport class tries to get the query body from the parameter POSTDATA. But that parameter does not exist. Instead the parmeter name depends on the HTTP method used for the request (see https://metacpan.org/dist/CGI/source/lib/CGI.pm#L656). So the HTTP::REST transport class should use those parameter names.