Ignore charset encoding in header

[jefioliveira]

I need to ignore the charset in the header.

Issue #15
issue #225

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[jefioliveira]

I signed it!

[natebosch]

cc @jonasfj

I'm not sure if this is breaking or not...

[natebosch]

We will need to run dartfmt and the body of the if needs to be wrapped in {}.

[ghost]

The PR description isn't very descriptive. Can you please edit it to say what this is and why we (all Dart HTTP users) need it?
The two referenced issues seem unrelated?

Have you considered how this will work with Request.encoding?

[ghost]

Ah, reviewing #184 I think I see that this PR is trying to address that issue specifically?

Parts of this change is a bit misleading since this doesn't really have anything to do with encoding, but is about whether we latch the charset on in Content-Type.
The way I see the problem is that there isn't really a mechanism for controlling the charset directly through the API, and it's automatically latch on where it really should be fully user controlled.
From skimming this, it doesn't really seem like an elegant solution to do that, so I think we might need to put some more thought into how we go about this.

Another aside is that something like this definitely needs tests.
We want to make sure we don't silently break clients who rely on the quirk of charset being set.

[mit-mit]

Closing as CLA wasn't signed