Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Rules list query can easily exceed default proxy header buffer sizes #148287

Open
weltenwort opened this issue Jan 3, 2023 · 1 comment
Open

Rules list query can easily exceed default proxy header buffer sizes #148287

weltenwort opened this issue Jan 3, 2023 · 1 comment
Assignees
@XavierM
Labels
bug Fixes for quality problems that affect the customer experience response-ops-mx-backlog ResponseOps MX backlog Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@weltenwort
Copy link
Member

ℹ️ Metadata

Kibana version: main, at least 136ed80
Original install method (e.g. download page, yum, from source, etc.): source

🐞 Description

When opening the rules page in Kibana stack monitoring it loads the table data with a GET request containing a very long list of query parameters. The default query is so long that, together with the authentication cookie and other headers, the request header size exceeds the buffer size in the default nginx and apache httpd configuration, which is set to 8 kB. This causes the server to respond with 414 Request URI too long and the rule table to remain unpopulated.

image

🔢 Steps to reproduce

  1. Deploy Kibana behind nginx or apache httpd configured as a reverse proxy.
  2. Navigate to the rules page in the stack management app.
  3. Observe that the request to load the rules list fails with a 414 response code.

🆗 Expected behavior

The filters are submitted in the request body so the header size is independent of the number and complexity of the filters.
@weltenwort weltenwort added bug Fixes for quality problems that affect the customer experience Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Jan 3, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@XavierM XavierM moved this from Awaiting Triage to Todo in AppEx: ResponseOps - Rules & Alerts Management Jan 5, 2023
@XavierM XavierM self-assigned this Jan 5, 2023
@XavierM XavierM mentioned this issue Jan 12, 2023
Merged
1 task
XavierM added a commit that referenced this issue Jan 12, 2023
@XavierM
Rule find post (#148836)
f2342fc 
## Summary

FIX -> #148287


### Checklist

- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
kibanamachine pushed a commit to kibanamachine/kibana that referenced this issue Jan 12, 2023
@XavierM
Rule find post (elastic#148836)
4c2ae0e 
## Summary

FIX -> elastic#148287

### Checklist

- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios

(cherry picked from commit f2342fc)
kibanamachine referenced this issue Jan 13, 2023
@kibanamachine @XavierM
[8.6] Rule find post (#148836) (#148865)
c0bd223 
# Backport

This will backport the following commits from `main` to `8.6`:
- [Rule find post
(#148836)](#148836)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Xavier
Mouligneau","email":"[email protected]"},"sourceCommit":{"committedDate":"2023-01-12T23:43:43Z","message":"Rule
find post (#148836)\n\n## Summary\r\n\r\nFIX ->
https://github.com/elastic/kibana/issues/148287\r\n\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"f2342fc3a88492b1083603912975424ec36352e6","branchLabelMapping":{"^v8.7.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","impact:high","Team:ResponseOps","v8.7.0","v8.6.1"],"number":148836,"url":"https://github.com/elastic/kibana/pull/148836","mergeCommit":{"message":"Rule
find post (#148836)\n\n## Summary\r\n\r\nFIX ->
https://github.com/elastic/kibana/issues/148287\r\n\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"f2342fc3a88492b1083603912975424ec36352e6"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.7.0","labelRegex":"^v8.7.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/148836","number":148836,"mergeCommit":{"message":"Rule
find post (#148836)\n\n## Summary\r\n\r\nFIX ->
https://github.com/elastic/kibana/issues/148287\r\n\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"f2342fc3a88492b1083603912975424ec36352e6"}},{"branch":"8.6","label":"v8.6.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/148858","number":148858,"state":"OPEN"}]}]
BACKPORT-->

Co-authored-by: Xavier Mouligneau <[email protected]>
jennypavlova pushed a commit to jennypavlova/kibana that referenced this issue Jan 13, 2023
@XavierM @jennypavlova
Rule find post (elastic#148836)
dfee7e9 
## Summary

FIX -> elastic#148287


### Checklist

- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
@pmuellr pmuellr mentioned this issue Jan 17, 2023
Merged
2 tasks
@cnasikas cnasikas added response-ops-mx-backlog ResponseOps MX backlog and removed Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Oct 29, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Oct 29, 2024
@wayneseymour wayneseymour added the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Nov 4, 2024
@botelastic botelastic bot removed the needs-team Issues missing a team label label Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@XavierM XavierM

Labels
bug Fixes for quality problems that affect the customer experience response-ops-mx-backlog ResponseOps MX backlog Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
No open projects
AppEx: ResponseOps - Rules & Alerts Management
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
6 participants
@XavierM @weltenwort @wayneseymour @cnasikas @elasticmachine @guskovaue