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 Is Version Manager 8.6.2 affected by CVEs that include Tomcat 8.5.42 as an affected release?
The HTTP header parsing code used an approach to end-of-line (EOL) parsing that allowed some invalid HTTP headers to be parsed as valid. This led 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 How to setup Tomcat / JBoss to make endpoint requests via a proxy
How to setup Tomcat / JBoss to make endpoint requests via a proxy
CMS-XML App Repository actions like deploy and create snapshot stuck in Waiting when using Smart Card and Tomcat proxied through IIS
App Repository actions like deploy and create snapshot stuck in Waiting when using Smart Card and Tomcat proxied through IIS
CMS-XML Using Smart Card (CAC) and Proxy Tomcat through IIS deploys and snapshots stay in waiting.
Using Smart Card (CAC) and Proxy Tomcat through IIS deploys and snapshots stay in waiting.
CMS-XML RESTGrid and RESTCaller and possibly other https calls originating in Tomcat does not work when the external proxy is configured.
1. Stop the SBM Tomcat and WWW services 2. Make a copy of common_config.bat typically found hereā€¦ C:\Program Files\Serena\SBM\Common\tomcat\bin\common_config.bat
CMS-XML Clustered Tomcat causes common services errors in Work Center
If we cluster Tomcat, we need to enforce stickiness with Tomcat. This KB handles the case where the Application Engine and Tomcat components are installed on the same server, and we are using IIS to proxy all connections.
CMS-XML uriworkermap.properties for tomcat cluster incorrectly set to worker1 instead of worker-local
When using Tomcat clustering with all components installed on two servers using IIS to proxy Tomcat requests and an external load balancer, some of the uriworkermap.properties are incorrectly set to worker1 instead of worker-local. Specifically the following are not be set worker-local when they should be (all the mappings in this file should be worker-local for this configuration):
CMS-XML Configuration changes required for Smart Card authentication when IIS is configured to proxy SBM requests
tab in SBM Configurator. This option disables all Tomcat HTTP connectors (8085, 8243, 8343, 8443). When you enable this option, you must perform the following additional steps to properly configure Smart Card authentication:
CMS-XML HTTP 404 error occurs on Tomcat cluster
Tomcat is running on IIS server for both servers Use IIS to proxy all connections Some Settings Added to IIRF.INI
CMS-XML Serena VM Web Application Server should use Tomcat 7.0.75
The code that parsed the HTTP request line permitted invalid characters. This could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a different interpretation, to inject data into the HTTP response. By manipulating the HTTP response the attacker could poison a web-cache, perform an XSS attack and/or obtain sensitive information from requests other than their own.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs