[jira] [Commented] (FLINK-5109) Invalid Content-Encoding Header in REST API responses

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on FLINK-5109:
---------------------------------------

GitHub user greghogan opened a pull request:

    https://github.com/apache/flink/pull/3432

    [FLINK-5109] [gelly] Interface for GraphAlgorithm results

    Create AlgorithmResult and AnalyticResult interfaces for library algorithms to implement. This flattens algorithm results to a single tuple.
    
    Also create interfaces for UnaryResult, BinaryResult, and TertiaryResult implementing methods to access the 0th, 1st, and 2nd vertices.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/greghogan/flink 5909_interface_for_graphalgorithm_results

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/3432.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3432
    
----
commit 4bd69c8dc173fa5a328c62f8ceb4878740801d27
Author: Greg Hogan <co...@greghogan.com>
Date:   2017-02-28T18:10:20Z

    [FLINK-5109] [gelly] Interface for GraphAlgorithm results
    
    Create AlgorithmResult and AnalyticResult interfaces for library
    algorithms to implement. This flattens algorithm results to a single
    tuple.
    
    Also create interfaces for UnaryResult, BinaryResult, and TertiaryResult
    implementing methods to access the 0th, 1st, and 2nd vertices.

----


> 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
>             Fix For: 1.2.0
>
>
> 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
(v6.3.15#6346)