Feedback
Did this article resolve your question/issue?

   

Article

Error in PASOE: Request header is too large

« Go Back

Information

 
TitleError in PASOE: Request header is too large
URL Nameerror-in-pasoe-request-header-is-too-large
Article Number000206050
EnvironmentProduct: OpenEdge
Version: 11.7.x, 12.x
OS: All supported platforms
Other: PASOE
Question/Problem Description

During implementation when accessing a Rest Service okta returns errors that token is  too large. Security was configured for the application using SAML Authentication.

 

 

 

 

 

Steps to Reproduce
Clarifying Information
- Request is sent from Postman and same error that token is too large is returned
- SAML token sent in Authentication header is about 15321 characters
Error MessageINFO: Error parsing HTTP request header
Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.
java.lang.IllegalArgumentException: Request header is too large
at org.apache.coyote.http11.Http11InputBuffer.fill(Http11InputBuffer.java:745)
at org.apache.coyote.http11.Http11InputBuffer.parseHeader(Http11InputBuffer.java:894)
at org.apache.coyote.http11.Http11InputBuffer.parseHeaders(Http11InputBuffer.java:598)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:524)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:818)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1623)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)
Defect Number
Enhancement Number
Cause
Http header size in PASOE is configured by default to 8192 and authentication header included a bigger string than the default size configured. 
Resolution
Update maxHttpHeaderSize parameter for http and/or https connectors with higher value. Follow these steps: 

1. Edit <pasoe-instance>\conf\server.xml file and find maxHttpHeaderSize
2. Set maxHttpHeaderSize to 65536
3. Save and restart PASOE instance
Workaround
Notes
Last Modified Date11/8/2021 4:46 PM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.