Skip to content

Multipart FilePart charset should be optional #524

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.

Sign up for GitHub

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

Jump to bottom
Closed
slandelle opened this issue Apr 3, 2014 · 0 comments
Closed

Multipart FilePart charset should be optional #524

slandelle opened this issue Apr 3, 2014 · 0 comments
Assignees
@slandelle
Labels
Enhancement
Milestone
1.8.5

Comments

@slandelle
Copy link
Contributor

Why would a file upload be by default in ISO-8859-1? How could a browser guess? Moreover, default transfer-encoding is binary!
@slandelle slandelle reopened this Apr 3, 2014
@slandelle slandelle changed the title Multipart charset should be optional Multipart FilePart charset should be optional Apr 3, 2014
slandelle pushed a commit that referenced this issue Apr 3, 2014
Make multipart FilePart charset optional, close #524
dee9671
@slandelle slandelle added this to the 1.8.5 milestone Apr 3, 2014
@slandelle slandelle self-assigned this Apr 3, 2014
cs-workco pushed a commit to cs-workco/async-http-client that referenced this issue Apr 13, 2023
@dnadoba
async/await execute (AsyncHttpClient#524)
5db7719 
* async/await execute

* remove default length for `HTTPClientRequest.Body`

* make redirect logic iterative

* move Task creation into `TransactionCancelHandler`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@slandelle slandelle

Labels
Enhancement
Projects
None yet
Milestone
1.8.5
Development

No branches or pull requests
1 participant
@slandelle