flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-5109) Invalid Content-Encoding Header in REST API responses
Date Sat, 03 Dec 2016 17:18:58 GMT

    [ https://issues.apache.org/jira/browse/FLINK-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15718416#comment-15718416

ASF GitHub Bot commented on FLINK-5109:

Github user greghogan commented on the issue:

    Unless a PR is urgent we typically allow a few days to see if any additional comments
come in from the community. This looks good so I'm merging it now. Thanks for the contribution!

> Invalid Content-Encoding Header in REST API responses
> -----------------------------------------------------
>                 Key: FLINK-5109
>                 URL: https://issues.apache.org/jira/browse/FLINK-5109
>             Project: Flink
>          Issue Type: Bug
>          Components: Web Client, Webfrontend
>    Affects Versions: 1.1.0, 1.2.0, 1.1.1, 1.1.2, 1.1.3
>            Reporter: Móger Tibor László
>              Labels: http-headers, rest_api
> On REST API calls the Flink runtime responds with the header Content-Encoding, containing
the value "utf-8". According to the HTTP/1.1 standard this header is invalid. ( https://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.5
> Possible acceptable values are: gzip, compress, deflate. Or it should be omitted.
> The invalid header may cause malfunction in projects building against Flink.
> The invalid header may be present in earlier versions aswell.
> Proposed solution: Remove lines from the project, where CONTENT_ENCODING header is set
to "utf-8". (I could do this in a PR.)
> Possible solution but may need further knowledge and skills than mine: Introduce content-encoding.
Doing so may need some configuration beacuse then Flink would have to encode the responses
properly (even paying attention to the request's Accept-Encoding headers).

This message was sent by Atlassian JIRA

View raw message