with its content type not FormData

Not specified by the original author.

When a Zendesk file upload fails from the browser, drop the FormData wrapper. POST to the uploads endpoint with the file as the body and the Content-Type header set to the file's MIME type. Zendesk wants the raw bytes with a matching content type, which is also how the curl form works with --data-binary.

Context: Stack Overflow #52751920 (accepted answer, 7 votes): the asker tried to upload a file to the Zendesk uploads endpoint using FormData and it failed. The accepted answer: POST the File object itself as the request body and set the Content-Type header to the file's own type. Zendesk expects the raw binary, not a multipart form.

Matched source

Source: Published skill Original query: "Zendesk uploads: POST the file as the body with its content type, not FormData" Key terms: body, content, file, formdata, post, type, uploads, zendesk

Source: Stack Overflow #52751920 (accepted answer, 7 votes): the asker tried to upload a file to the Zendesk uploads endpoint using FormData and it failed. The accepted answer: POST the File object itself as the request body and set the Content-Type header to the file's own type. Zendesk expects the raw binary, not a multipart form.

Verified resolution: When a Zendesk file upload fails from the browser, drop the FormData wrapper. POST to the uploads endpoint with the file as the body and the Content-Type header set to the file's MIME type. Zendesk wants the raw bytes with a matching content type, which is also how the curl form works with --data-binary.

Source URL: https://stackoverflow.com/questions/52751920/uploading-a-binary-file-using-fetch

Not specified by the original author.

TL;DR

Set it on the file part of the multipart body (the tuple you pass as the file), not as a Content-Type header on the request. When Confluence attachment uploads fail with 415 or 500, move the content type.

Steps

1. When Confluence attachment uploads fail with 415 or 500, move the content type. Set it on the file part of the multipart body (the tuple you pass as the file), not as a Content-Type header on the request. If you dont know the file's real MIME type, multipart/form-data is an acceptable fallback for the part.

When to use

You are seeing this: When Confluence attachment uploads fail with 415 or 500, move the content type. Use this skill when you run into "Confluence REST API: put the content type on the file part, not the request header".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Stack Overflow #35286227 (accepted answer, 6 votes): the asker uploaded attachments with Python requests and got 415 unsupported media type or 500 errors depending on how the request was built. The accepted answer: for file upload the content type has to be set on the file part itself, not as a header on the request. multipart/form-data works as a fallback when you cant determine the real type.

Verified resolution: When Confluence attachment uploads fail with 415 or 500, move the content type. Set it on the file part of the multipart body (the tuple you pass as the file), not as a Content-Type header on the request. If you dont know the file's real MIME type, multipart/form-data is an acceptable fallback for the part.

Source URL: https://stackoverflow.com/questions/35286227/uploading-attachments-to-confluence-rest-api-with-python-requests-gives-415-and-500-erro

Not specified by the original author.

TL;DR

[sina-salahshour (reporter)]: Change the import to a namespace import: import * as formData from 'form-data' instead of the default import. Confirmed fixed by the reporter.

Steps

1. [sina-salahshour (reporter)]: Change the import to a namespace import: import * as formData from 'form-data' instead of the default import. Default-importing form-data breaks the FormData constructor mailgun.js expects, which throws at runtime under NestJS. Confirmed fixed by the reporter.

When to use

You are seeing this: mailgun/mailgun-js#339: Issue mailgun/mailgun-js#339 (closed, 7 comments): Using mailgun.js with NestJS, no type errors, but at runtime new Mailgun(formData) throws a form-data error. Use this skill when you run into "form-data runtime error under NestJS: use namespace import".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Issue mailgun/mailgun-js#339: the reporter asked: Issue mailgun/mailgun-js#339 (closed, 7 comments): Using mailgun.js with NestJS, no type errors, but at runtime new Mailgun(formData) throws a form-data error. Code: import formData from 'form-data'; import Mailgun from 'mailgun.js'; ... this.mailgun = new Mailgun(formData); The verified answer was: [sina-salahshour (reporter)]: Change the import to a namespace import: import * as formData from 'form-data' instead of the default import. Default-importing form-data breaks the FormData constructor mailgun.js expects, which throws at runtime under NestJS. Confirmed fixed by the reporter. Evidence thread: https://github.com/mailgun/mailgun-js/issues/339