[
https://issues.apache.org/jira/browse/CALCITE-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14697458#comment-14697458
]
Nick Dimiduk commented on CALCITE-780:
--------------------------------------
What [~lukaslalinsky] said -- I'm all for simple things like having a query
exposed via url, but for all the years i've putzed with HTML, i actually have
no idea how to build an anchor tag that includes a header. Maybe you're
thinking of the request parameters passed in the [query
string|https://en.wikipedia.org/wiki/Query_string]? This is not the same as
request headers.
> HTTP error 413 when sending a long string to the Avatica server
> ---------------------------------------------------------------
>
> Key: CALCITE-780
> URL: https://issues.apache.org/jira/browse/CALCITE-780
> Project: Calcite
> Issue Type: Bug
> Components: avatica
> Reporter: Lukas Lalinsky
> Assignee: Julian Hyde
> Fix For: 1.4.0-incubating
>
>
> When I try to execute a query with a very long string, the server returns
> error 413 "entity too large". My assumption is that this happens, because the
> RPC uses a HTTP header to pass the RPC request data and most HTTP parsers do
> not like long headers. The best solution would be to use the body of the HTTP
> request. It could be made backward-compatible, by checking the header first
> and if it's missing, then read the body.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
