Home - Forums-.NET - FlyTreeView (ASP.NET) - Using FlyTreeView in ISA proxy environment

FlyTreeView (ASP.NET)

Technical support and KB related to the FlyTreeView control

This forum related to following products: FlyTreeView for ASP.NET

Using FlyTreeView in ISA proxy environment
Link Posted: 19-Feb-2006 21:06
Hi,

I have a wierd problem running the tree in a proxy environment. When i use it on a regular page it works brilliantly, but this was during the development process. When I moved to test environment I was needed to test my pages through ISA proxy because this is how we work in our orginazation. When I configured a rule on one proxy that redirect requests for the page to my web server it still worked.

The problem started when I used two proxies, which is the architecture  of web access in our intranet. The user is surfing to the first proxy with the needed virtual path; Then it is redirected to the second proxy with the same virtual path; And finally the second proxy redirect the page to the web server where the real page exist, and the response is handled in an opposite way. First when the tree is rendered it works fine, but when I try to expand a node it throws me the following message: "Error occurd. Description: Error while parsing loaded data. Details: Only one top level element is allowed in an xml document" followed by two regulat javascript errors of uncaught exception in flytreeview.htc and node.htc.

I would glad to hear any solution or idea about this, but please do not ask me why we work in two proxies environment as it's really not my call.

Thanks!
Link Posted: 20-Feb-2006 13:08
When you get the error you described, it means that the XML data loaded on demand  is not a valid XML document. Probably some exception occures on your server and it renders error html instead.

Please load the page used as NodeSrc in a separate browser window. And see whether what you get is a valid XML and not an exception report from ASP.NET.
You can get the error description if it is an ASP.NET error.

Also you can check the following URL and say what happens when you try to expand nodes:
http://www.truedotnet.com/asp.net/treeview/demos.aspx?demo=style_common&default=Classic