[
https://issues.apache.org/jira/browse/CALCITE-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14660673#comment-14660673
]
Lukas Lalinsky commented on CALCITE-780:
----------------------------------------
You can't actually do requests by clicking on URLs, because you can't set an
HTTP header that way and you can do requests with JSON body with curl by using
the -d option.
I assumed the server supported both for compatibility reasons. I was a bit
surprised that the client used both depending on the request, but I assumed it
was intentional, so I didn't comment on that before.
> 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)
