Details
-
Bug
-
Resolution: Fixed
-
Low
-
5.7, 5.7.1, 5.7.3
-
None
Description
Summary
When using Apache as a proxy in front of Confluence, and using the SSL connector in Apache, some functions in Confluence can cause Apache with SSL to stop responding (Confluence is still running behind the scenes).
Environment
- Apache HTTP Server
- Default LimitRequestLine (set to 8190)
- SSL configured in Apache
Steps to Reproduce
- Install Confluence 5.7.x
- Create a page with a Roadmap macro
- Add 20 bars to the roadmap (this is in addition to the default 3 bars)
- Click insert
- Click save
Expected Results
The page loads in Confluence and is served through Apache to the user
Actual Results
The page loads in Confluence (I confirmed this through profile logging), but is not served through Apache (the user is unable to access the server for a period of roughly 10 minutes after this failure)
The following appears in the https_error_log:
[Mon Apr 27 14:09:23 2015] [error] [client xx.xxx.xxx.xx] request failed: URI too long (longer than 8190)
Notes
It looks like this issue can be fixed by switching to POST instead of GET when loading pages like this (the large amount of objects in the roadmap is passed through the GET and caused the issue in Apache)
Workaround
Add a line to the virtual host file to increase the LimitRequestLine from the default of 8190. Doubling the value should be a good start.