XML Reporting Element URI Redirect

We were able to resolve this issue. What we discovered was that the server had HTTP compression enabled which caused the XML data to be compressed as it passed through the LTM. We originally missed this because our friendly tcpdump tool, Ethereal, was automatically decompressing the HTTP data and displaying it. We modified the HTTP profile to remove the Accept-Encoding header and the STREAM profile began working. XML awareness was not required.

 

 

The LTM was licensed for HTTP compression so we enabled that in the HTTP profile and removed the setting that erased the Accept-Encoding header thinking that the default compression settings would remove that header for us. There's a checkbox in the compression section to remove the header. Unfortunately, that broke the STREAM profile again.

 

 

The moral of this story is that, regardless of enabling HTTP compression, we had to make sure that the Accept-Encoding header was erased in the HTTP profile to get the STREAM profile to work correctly.

 

 

Dave