The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
It is possible to see errors around the Web HTTP Save File Activity that reference "The server committed a protocol violation. Section=ResponseStatusLine". As a result, the file for the activity is not received.
There are no specific requirements for this document.
The information in this document is based on Tidal Enterprise Orchestrator (TEO) 2.2 or later.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Refer to Cisco Technical Tips Conventions for more information on document conventions.
The issue is that the file is not received from the Web HTTP Save File.
While the solution is ongoing, in TEO 2.2, the user can add a setting in the main server configuration file.
Complete these steps:
Add this line to the Tidal.Automation.Server.Exe.Config file:
<system.net> <settings> <httpWebRequestuseUnsafeHeaderParsing = "true"/> </settings> </system.net>
The user can add a couple of settings to the actual activity. For example, set the HTTP Headers Content Type to application/x-www-form-urlencoded and set the Request field on the HTTP Request tab to userName=tpsuper&password.password=<tpSuperpassword>.
Note: The password should be a variable reference to an encrypted string.