Skip to content

Wrong endpoint generation (files api) #27

@joeriakkerman

Description

@joeriakkerman

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" }

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions