<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=325068) </details> <!--IssueSummary end--> This issue originates from gitlab-org/gitlab-ce#63097 Our [NPM package](/gitlab-org/gitlab-ee/issues/5934) doesn't have workhorse upload acceleration, and members of the wider community are contributing new features based on that https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/9012#note_179607151 The reason being is that we don't have a body hijacking handler for JSON encoded requests. What happens with these kinds of uploads is that a file is provided in base64 encoding inside the JSON body. [This](https://gitlab.com/gitlab-org/gitlab-ee/blob/master/ee/app/services/packages/create_npm_package_service.rb#L19) is how we handle NPM gitlab-workhorse~3612448 uploading on rails side. ## Proposal We should implement a handler that can hijack JSON encoded body, stripping base64 encoded files and replacing them with the usual metadata workhorse generates on upload acceleration. /cc @marin @dzaporozhets