Request-URI Too Large in the Web Console
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 17.3k
- Forks
- 1.7k
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 28
Description
To reproduce
- Go to the Web Console
- Run a query with a lot of text e.g. against a table with lots of columns
Expected result: the query runs
Actual result: 414 "Request-URI Too Large"
QuestDB version:
9.0.3
OS, in case of Docker specify Docker and the Host OS:
Ubuntu (Docker)
File System, in case of Docker specify Host File System:
ext4
Full Name:
Freddy Rios
Affiliation:
Copenhagen Atomics
Have you followed Linux, MacOs kernel configuration steps to increase Maximum open files and Maximum virtual memory areas limit?
- Yes, I have
Additional context
The browser's developer tools confirms the query is sent as a query string parameter, which introduces a hard limitation on the request size. Changing to a POST request and sending it in the body usually greatly increases the limit.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Web Console query request entry point and reproduce the 414 error with a query containing lots of text. Trace how the query is sent, then verify that large queries are accepted and execute successfully without exceeding the request URI limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100