Repository navigation
Conversation
The plugin execute request was built as '?params=...;async&=<0|1>', which the server splits into an invalid empty-named '=<0|1>' chunk. Newer Artifactory versions reject it (HTTP 500 on 7.146.x, HTTP 400 'Malformed request parameters' on 7.173.x). Build it as '&async=<0|1>' instead.
itsmeleela
approved these changes
Nov 17, 2026
This file contains hidden or 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
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.
Problem
PluginHandleImpl.doExecutebuilds the request as?params=k=v;async&=<0|1>. The server splits this on&intoparams=k=v;asyncand an empty-named chunk=<0|1>. Older Artifactory versions silently ignored the bad chunk; newer ones reject it:Invalid chunk starting at byte [24] and ending at byte [26] with a value of [=0] ignoredMalformed request parametersFix
Build the parameter as
&async=<0|1>, giving?params=k=v;&async=0(and?params=&async=0when there are no params).Behavior note
Because the old
asyncflag never reached the server as a real parameter,aSync()effectively ran synchronously on tolerant servers. With this fixaSync()actually requests async execution. No API signatures change.Testing
Reproduced the 500 with 2.21.2 on Artifactory 7.146.45 and confirmed the fix on 7.146.45 and 7.173.17 (reported by the customer's engineer). No unit test added: the URL is built inline and existing plugin tests need a live server.