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 Invalid characters being passed in ZMF REST Service HTTP headers
Invalid characters being passed in ZMF REST Service HTTP headers
CMS-XML In 11.3 Configurator can now easily enable the following secure response HTTP header options for IIS and Tomcat
In 11.3 Configurator can now easily enable the following secure response HTTP header options for IIS and Tomcat
CMS-XML CU: Custom HTTP header does not work if typed in lower case
CU: Custom HTTP header does not work if typed in lower case
CMS-XML charset specification missing from HTTP header in WS responses
charset specification missing from HTTP header in WS responses
CMS-XML Vul ID: V-69375 / STIG ID: APSC-DV-000680 - The application must provide audit record generation capability for HTTP headers
Vul ID: V-69375 / STIG ID: APSC-DV-000680 - The application must provide audit record generation capability for HTTP headers
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. http 11. Http 11Processor.service Error parsing HTTP request header error shows in the Catalina logfile.
CMS-XML HTTP 400 - Bad Request (Request Headers too long)
HTTP 400 - Bad Request (Request Headers too long) - Chrome The Web Page cannot be found HTTP 400 - Internet Explorer This typically happens when SBM uses Windows Domain (NTCR) authentication.
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."
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."
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 HTTP 405 error from IIS on SSO login redirect
An HTTP 405 error is received when trying to login via SSO if the referer header is only a host name (ie " http ://host/") which the SSO server uses as a "return" URL.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs