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

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

GitHub user Hapcy opened a pull request:

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

    [FLINK-5109] fix invalid content-encoding header of webmonitor

    Thanks for contributing to Apache Flink. Before you open your pull request, 
please take the following check list into consideration.
    If your changes take all of the items into account, feel free to open your 
pull request. For more information and/or questions please refer to the [How To 
Contribute guide](http://flink.apache.org/how-to-contribute.html).
    In addition to going through the list, please provide a meaningful 
description of your changes.
    
    - [x] General
      - The pull request references the related JIRA issue ("[FLINK-XXX] Jira 
title text")
      - The pull request addresses only one issue
      - Each commit in the PR has a meaningful commit message (including the 
JIRA id)
    
    - [x] Documentation --- not touched
      - Documentation has been added for new functionality
      - Old documentation affected by the pull request has been updated
      - JavaDoc for public methods has been added
    
    - [x] Tests & Build
      - Functionality added by the pull request is covered by tests
      - `mvn clean verify` has been executed successfully locally or a Travis 
build has passed --- Travis build failed but I had nothing to do with those 
parts of the code.
    
    I'm kind of newbie and some other people's commits showed up as commited 
with me but I have nothing to do with them.

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

    $ git pull https://github.com/Hapcy/flink master

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

    https://github.com/apache/flink/pull/2892.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 #2892
    
----
commit 7f1c76de5d2fb54ff4e9836a38bc537098649fb4
Author: tibor.moger <tibor.mo...@smartx.eu>
Date:   2016-11-28T15:51:47Z

    [FLINK-5109] fix invalid content-encoding header of webmonitor

commit 2a305c54dee1644fd787ec2d707b57c74a6b45f6
Author: Aljoscha Krettek <aljoscha.kret...@gmail.com>
Date:   2016-11-02T10:06:01Z

    [FLINK-4993] Don't Allow Trigger.onMerge() to return TriggerResult
    
    Allowing Trigger.onMerge() to return a TriggerResult is not necessary
    since an onMerge() call will always be followed by an onElement() call
    when adding the element that caused the merging to the merged window.
    Having this complicates the internal logic of the WindowOperator and
    makes writing Triggers more confusing than it has to be.

commit ad9f8dbd6aa0a460c2f763ec1041130f44beeaad
Author: Aljoscha Krettek <aljoscha.kret...@gmail.com>
Date:   2016-11-11T09:57:25Z

    [FLINK-5026] Rename TimelyFlatMap to Process

commit ff3470991d0c620ae3ccedeb1326c331c9cfa443
Author: twalthr <twal...@apache.org>
Date:   2016-11-17T13:17:23Z

    [FLINK-4872] [types] Type erasure problem exclusively on cluster execution
    
    This closes #2823.

commit 5d4ececb310d0d3d0d01934cb6015766bb17ca65
Author: sergey_sokur <sokur...@gmail.com>
Date:   2016-11-17T16:28:20Z

    [FLINK-5050] [build] Remove transitive JSON.org dependency
    
    This transitive dependency has an incompatible license.
    
    This closes #2824

commit 764739de663d1bc8de981bd7508f3aa03a4a6a0b
Author: Aljoscha Krettek <aljoscha.kret...@gmail.com>
Date:   2016-11-23T11:13:05Z

    [FLINK-5181] Add Tests in StateBackendTestBase that verify Default-Value 
Behaviour

commit ba61d43c87b5228c689a10156950880ffbe23b2f
Author: Stephan Ewen <se...@apache.org>
Date:   2016-11-23T14:37:05Z

    [hotfix] Flush in CsvOutputFormat before closing, to increase CI stability

commit 5cd7eb0042c71839c610f25765ac1834561bffb3
Author: Stephan Ewen <se...@apache.org>
Date:   2016-11-23T14:54:15Z

    [hotfix] [tests] Harden timeout logic for TaskManager registration in 
AbstractTaskManagerProcessFailureRecoveryTest

commit dc51242a4cede4684614c86afa0d0724898343b7
Author: shijinkui <shijin...@huawei.com>
Date:   2016-11-26T08:14:13Z

    [FLINK-5168] Scaladoc annotation link use [[]] instead of {@link}
    
    This closes #2875

commit 3ce3e104641728930f7d53a3308b74dac5cd15e5
Author: Aljoscha Krettek <aljoscha.kret...@gmail.com>
Date:   2016-11-28T12:51:51Z

    [FLINK-4993] Remove Unused Import in TriggerResult

commit bb2e2d0fc2eae2a65839e937cebe0034ab81a75d
Author: Stephan Ewen <se...@apache.org>
Date:   2016-11-28T13:55:31Z

    [hotfix] [docs] Add a rouch description about internal types of states and 
state backends

----


> 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
(v6.3.4#6332)

Reply via email to