Skip to content

Allow setting of accepted content encodings and charset #6

Description

@erickok

Although the defaults make a lot of sense, sometimes a server doesn't play nice and you need to set a specific content encoding and character set to be accepted. For example, teh webserver I am talking to claims to support gzipped content, but often returns scrambled data when I ask for it.

I suggest keeping the defaults in place but allow setting of content encodings and charset on the HttpClient, so these settings are used in any successive http request.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions