Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML DimCM: Tomcat: org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header error shows in the Catalina logfile.
DimCM: Tomcat: org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header error shows in the Catalina logfile.
CMS-XML HTTP 400 - Bad Request (Request Headers too long)
Under some circumstances individual users may receive the following error message on the browser when attempting to log on to User Workspace, Work Center or Application Repository. HTTP 400 - Bad Request (Request Headers too long) - Chrome The Web Page cannot be found HTTP 400 - Internet Explorer
CMS-XML Composer cannot connect to repository "Connection attempt failed. Could not connect to the Repository. An HTTP Content-Type header is required for SOAP messaging and none was found."
If the timezone on your client has a clock time that is different then you may get the following error from Composer:
CMS-XML SBM: Can log into Work Center, but Repository gives error: HTTP Status 412 – Precondition Failed
HTTP Status 412 – Precondition Failed Type Status Report Description One or more conditions given in the request header fields evaluated to false when tested on the server.
CMS-XML WebSocket console error, can't connect to Deployment Automation using proxy HTTP protocol
In this scenario, the connection will probably fail. The browser does not issue the HTTP CONNECT method and when the proxy server forwards a request through the WebSocket to the server, it is expected to strip off the connection header . Because it doesn't know to do that, the handshake will typically fail immediately.
CMS-XML Tomcat 7.0.25 Vulnerabilities
The checks that limited the permitted size of request headers were implemented too late in the request parsing process for the HTTP NIO connector. This enabled a malicious user to trigger an OutOfMemoryError by sending a single request with very large headers.
CMS-XML Is Version Manager 8.6.2 affected by CVEs that include Tomcat 8.5.42 as an affected release?
The refactoring in 8.5.48 introduced a regression. The result of the regression was that invalid Transfer-Encoding headers were incorrectly processed leading to a possibility of HTTP Request Smuggling if Tomcat was located behind a reverse proxy that incorrectly handled the invalid Transfer-Encoding header in a particular manner. Such a reverse proxy is considered unlikely.
CMS-XML Some users get "Bad Request" error when attempting to login when they get redirected to the IDP login url.
Request header is too large ... .parseHeaders( Http 11InputBuffer. ... at org.apache.coyote.http11.Http11Processor.service( Http 11Processor.java:699) [tomcat-coyote.jar:8.5.13] ... If they still get the same error and you see the same error in the Tomcat.log file try these steps again and increase the maxHttpHeaderSize to 32768
CMS-XML Using the RESTCaller SOAP wrapper utility service but get "No compatible tokens found on the request" in soap response.
... see the following error in the Common ... ... soapenv=' http :// ... ... <soapenv: Header > ... /soapenv: Header > ... <soapenv: Fault xmlns:soapenv=' http :// ... ... wsse=' http :// ... <faultstring>No compatible tokens found on the request </faultstring> ... <detail>No compatible tokens found on the request </detail> </soapenv: Fault > ... Try your orchestration again and verify the error goes away.
CMS-XML Internal Server Error HTTP 500.24 The request is not supported. (0x80070032)
Internal Server Error HTTP 500.24 The request is not supported. (0x80070032)
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Title: Dimensions CM: Deploying Emergency Fixes (demonstration)
This demonstration shows you how to deploy an emergency fix to a live production environment in Dimensions CM. You will learn how to promote requests to any stage in the Global Stage Lifecycle, promote and deploy in the same operation, and browse deployment areas.
Title: Dimensions CM: Scheduling Deployment (demonstration)
This demonstration shows you how to schedule a deployment in Dimensions CM. You will learn how to set a deployment sequence, schedule a deployment, and use the Queue tab in the Deployment view

Additional Assistance

  • Submit a Case Online
  • FAQs