[
https://issues.apache.org/jira/browse/FLINK-7565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Metzger updated FLINK-7565:
----------------------------------
Description:
I tried sending some REST calls to Flink's web UI, using a HTTP 1.1 client
(Jersey-client 2.23.1), using chunked transfer encoding (which means the
content-length header is not set).
Flink's web Ui treats those requests as empty requests (with no body), leading
to errors and exceptions.
Its probably "just" an upgrade of netty-router or so to fix this?
I've also found a good workaround for my use case (by setting
setChunkedEncodingEnabled(false)) (See also
https://stackoverflow.com/questions/18157218/jersey-2-0-content-length-not-set)
> Add support for HTTP 1.1 (Chunked transfer encoding) to Flink web UI
> --------------------------------------------------------------------
>
> Key: FLINK-7565
> URL: https://issues.apache.org/jira/browse/FLINK-7565
> Project: Flink
> Issue Type: Improvement
> Components: Webfrontend
> Reporter: Robert Metzger
> Fix For: 1.4.0
>
>
> I tried sending some REST calls to Flink's web UI, using a HTTP 1.1 client
> (Jersey-client 2.23.1), using chunked transfer encoding (which means the
> content-length header is not set).
> Flink's web Ui treats those requests as empty requests (with no body),
> leading to errors and exceptions.
> Its probably "just" an upgrade of netty-router or so to fix this?
> I've also found a good workaround for my use case (by setting
> setChunkedEncodingEnabled(false)) (See also
> https://stackoverflow.com/questions/18157218/jersey-2-0-content-length-not-set)
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
