Forum Discussion
Lucas_Thompson_
Historic F5 Account
You'll need to either decrypt it, or just set it to communicate on port 80. Citrix servers generally allow the comms to be 443 or 80.
The SSLDUMP we use is generally the same as the normal ssldump, so the use (and how to decrypt it) is the same. Two rules:
- Make sure the SSL session cache is deleted so you get a new SSL session ID, otherwise the decryption can't work. In your case this would be for the serverssl profile, not the clientssl profile because you're trying to decrypt the serverside of the connection.
- As you've done, DH ciphers have to be disabled.
I see that you have a support case on this already. As soon as we can see the backend comms, we'll have a better idea about what's happening. I can't find any reference to this error in any other support case except one where somebody was trying to get VMWare Horizon View to function via APM. The symptoms for that one were nearly identical (including the 'TTP /1.1' part) but it doesn't look like there was any followup or resolution.
Jacob_Newfield1
Dec 21, 2015Historic F5 Account
There shouldn't be a redirect from the Storefront server for PNAgent communications, i.e. even if the parse error is corrected the overall functionality will fail. The BIG-IP/APM should be configured to translate ingress client-side requests from "/Citrix/PNAgent/config.xml" into egress server-side request "/Citrix/PNAgent/[store]/config.xml" which is accomplished via an iRule data group entry named "APM_Citrix_ConfigXML" with key/value pair "[vs_fqdn] := /Citrix/[store]/PNAgent/config.xml".
The APM supports the Storefront protocol where the URI "/Citrix/PNAgent/config.xml" would not be used. However, if the PNAgent protocol is required or desired then be sure to configure the client with a case sensitive PNAgent URI, i.e. "/Citrix/PNAgent/config.xml" and not ""/Citrix/PNAgent/Config.xml".