Skip to content
This repository has been archived by the owner on Mar 13, 2021. It is now read-only.

Handle Content-Type headers with a charset #30

Merged
merged 1 commit into from
Feb 20, 2018

Conversation

scothis
Copy link
Member

@scothis scothis commented Feb 20, 2018

The Content-Type header can also contain a charset param.

Content-Type: text/plain; charset=utf-8

Previously this would cause the gRPC handler to choke. Now the charset
is ignored. In the future we should correctly parse the charset and
decode the payload accordingly. For now, all text content is assumed to
be utf-8.

Fixes: #29

The Content-Type header can also contain a charset param.

```http
Content-Type: text/plain; charset=utf-8
```

Previously this would cause the gRPC handler to choke. Now the charset
is ignored. In the future we should correctly parse the charset and
decode the payload accordingly. For now, all text content is assumed to
be utf-8.

Fixes: projectriff#29
@scothis scothis merged commit 86ddf06 into projectriff:master Feb 20, 2018
@scothis scothis deleted the grpc-charset branch February 20, 2018 14:32
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant