Skip to content

Wrong endpoint generation (files api) #27

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
joeriakkerman opened this issue Apr 28, 2025 · 0 comments
Open

Wrong endpoint generation (files api) #27

joeriakkerman opened this issue Apr 28, 2025 · 0 comments

Comments

@joeriakkerman
Copy link

Within the FilesApiService.CrmFilesPost(ctx context.Context, file *os.File, localVarOptionals *CrmFilesPostOpts) (FileData, *http.Response, error) function, the file argument is never being used, which causes the response to always contain a 400 Bad Request, since the form data is not being filled with the required data and thus, the boundary header will not be set correctly:
{ "message" : "parse multipart form: no multipart boundary param in Content-Type" }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant