Investigate if charset header really should be added to all content-types

sahaya / rest-assured

Automatically exported from code.google.com/p/rest-assured

0 stars 0 forks source link

Investigate if charset header really should be added to all content-types #380

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

For example content-type image/jpg should probably not have a charset added 
since it's binary. Perhaps bring back the old method in EncoderConfig where it 
was possible to disable charset for binary content types? Or just disable the 
automatic adding of content-type by default?

Original issue reported on code.google.com by johan.ha...@gmail.com on 30 Dec 2014 at 9:09