-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Content Type of file uploaded in multipart/form-data request #271
Comments
Not sure exactly how close you need it to the original, but this might be a good starting point:
|
I cannot make it provide Content-Type header inside the multipart/form-data container, and that is essential in our case. |
@myroslav it's a bug/missing feature. Will look into that. |
Would it be possible to use a curl-like syntax with semicolon?
|
@jeltz yes, good idea |
yeah, it would be cool if this thing can get in. do you know when? |
+1 |
1 similar comment
👍 |
🎉 |
NOTES: * Httpie does not currently support setting the content type for each part in a multipart form -- these multipart types are currently ignored. See: httpie/cli#199 httpie/cli#271 httpie/cli#285 httpie/cli#398 * There is an issue with specifying piped input for multipart form data. There is no way currently to specify the data without specifying a filename parameter in the Content-Disposition. For now, this is ignored. See: httpie/cli#342
NOTES: * Httpie does not currently support setting the content type for each part in a multipart form -- these multipart types are currently ignored. See: httpie/cli#199 httpie/cli#271 httpie/cli#285 httpie/cli#398 * There is an issue with specifying piped input for multipart form data. There is no way currently to specify the data without specifying a filename parameter in the Content-Disposition. For now, this is ignored. See: httpie/cli#342
NOTES: * Httpie does not currently support setting the content type for each part in a multipart form -- these multipart types are currently ignored. See: httpie/cli#199 httpie/cli#271 httpie/cli#285 httpie/cli#398 * There is an issue with specifying piped input for multipart form data. There is no way currently to specify the data without specifying a filename parameter in the Content-Disposition. For now, this is ignored. See: httpie/cli#342
NOTES: * Httpie does not currently support setting the content type for each part in a multipart form -- these multipart types are currently ignored. See: httpie/cli#199 httpie/cli#271 httpie/cli#285 httpie/cli#398 * There is an issue with specifying piped input for multipart form data. There is no way currently to specify the data without specifying a filename parameter in the Content-Disposition. For now, this is ignored. See: httpie/cli#342
This commit adds support for generating a snippet that contains the HTTPie command for the request. As the snippet does not require any additional configuration, it has added to the existing default snippets. Httpie does not currently support setting the content type for each part in a multipart form -- these multipart types are currently ignored. See: httpie/cli#199 httpie/cli#271 httpie/cli#285 httpie/cli#398 There is an issue with specifying piped input for multipart form data. There is no way currently to specify the data without specifying a filename parameter in the Content-Disposition. For now, this is ignored. See: httpie/cli#342 See gh-207
curl support file Content-Type via following syntax:
It look like the content it generates is something like:
And I cannot achieve the same result in HTTPie. Any hints are appreciated.
The text was updated successfully, but these errors were encountered: