Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 41293200C29 for ; Tue, 28 Feb 2017 22:54:54 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 3FC10160B7C; Tue, 28 Feb 2017 21:54:54 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 8AC67160B59 for ; Tue, 28 Feb 2017 22:54:53 +0100 (CET) Received: (qmail 97252 invoked by uid 500); 28 Feb 2017 21:54:52 -0000 Mailing-List: contact issues-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list issues@flink.apache.org Received: (qmail 97242 invoked by uid 99); 28 Feb 2017 21:54:52 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Feb 2017 21:54:52 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 583D918DBE9 for ; Tue, 28 Feb 2017 21:54:52 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -2.346 X-Spam-Level: X-Spam-Status: No, score=-2.346 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-2.999, SPF_NEUTRAL=0.652, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id PL0sEICIywnm for ; Tue, 28 Feb 2017 21:54:47 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 9ED5860E17 for ; Tue, 28 Feb 2017 21:54:47 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 6970AE088A for ; Tue, 28 Feb 2017 21:54:46 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id A4ED92416E for ; Tue, 28 Feb 2017 21:54:45 +0000 (UTC) Date: Tue, 28 Feb 2017 21:54:45 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: issues@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FLINK-5109) Invalid Content-Encoding Header in REST API responses MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 28 Feb 2017 21:54:54 -0000 [ https://issues.apache.org/jira/browse/FLINK-5109?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1588= 8927#comment-15888927 ]=20 ASF GitHub Bot commented on FLINK-5109: --------------------------------------- Github user greghogan closed the pull request at: https://github.com/apache/flink/pull/3432 > 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=C3=B3ger Tibor L=C3=A1szl=C3=B3 > Labels: http-headers, rest_api > Fix For: 1.2.0 > > > On REST API calls the Flink runtime responds with the header Content-Enco= ding, containing the value "utf-8". According to the HTTP/1.1 standard this= header is invalid. ( https://www.w3.org/Protocols/rfc2616/rfc2616-sec3.htm= l#sec3.5 )=20 > Possible acceptable values are: gzip, compress, deflate. Or it should be = omitted. > The invalid header may cause malfunction in projects building against Fli= nk. > 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: In= troduce content-encoding. Doing so may need some configuration beacuse then= Flink would have to encode the responses properly (even paying attention t= o the request's Accept-Encoding headers). -- This message was sent by Atlassian JIRA (v6.3.15#6346)