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.

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

Add documentation for SSLRenegBufferSize in Apache configuration #1936

Open
taojing2002 opened this issue Jun 17, 2024 · 2 comments
Open

Add documentation for SSLRenegBufferSize in Apache configuration #1936

taojing2002 opened this issue Jun 17, 2024 · 2 comments
Milestone

Comments

@taojing2002
Copy link
Contributor

Sometimes we may see errors on the client side like:

<html><head>
  <title>413 Request Entity Too Large</title>
  </head><body>
  <h1>Request Entity Too Large</h1>
  The requested resource does not allow request data with POST requests, or the amount of data provided in
  the request exceeds the capacity limit.
  <hr>
  <address>Apache/2.4.52 (Ubuntu) Server at smithsonian.dataone.org Port 443</address>
  </body></html>

Also in the apache error log:

[ssl:error] [pid 1577432:tid 140187447318080] [client 128.111.85.174:54024] AH02018: request body exceeds maximum size (131072) for SSL buffer

Those errors need to increase the property in the apache configuration file:

<Location "/metacat/d1/mn">
                SSLRenegBufferSize 10000000
 </Location>                       

Currently we don't have this section on documentation. We need to add it.

@taojing2002 taojing2002 added this to the 3.1.0 milestone Jun 17, 2024
@iannesbitt
Copy link

@taojing2002 The other thing I had to do in order to get the Smithsonian Metacat to accept files larger than 10000000 bytes was uncomment SSLOptions +OptRenegotiate.

@artntek
Copy link
Contributor

artntek commented Jul 4, 2024

for nginx/k8s, no directly comparable params, but see PR #1942 for annotations to deal better with larger request sizes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants