Forum Discussion
Michael_Koyfma1
Sep 21, 2012Cirrus
Hamish,
There are two issues that cause the problem with XenApp 4.5
The response from 4.5 XML broker violates HTTP standard in two ways:
1) It has 'Transfer-Coding' header instead of 'Transfer-Encoding' <-- this one is easy to fix with iRules
2) It does not have a trailing CRLF as dictated by RFC. <-- this one is not so easy and requires layered virtuals and non-the-shortest iRule to fix - so getting it done on the XenApp server itself is the best way to go.
Hope it helps.