Home - Forums-.NET - FlyTreeView (ASP.NET) - Callback issue, communication port configuration

FlyTreeView (ASP.NET)

Technical support and KB related to the FlyTreeView control

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

Callback issue, communication port configuration
Link Posted: 29-Apr-2009 03:14
We got an issue with one of our client who uses our web app that utilizes FlyTreeView.
When used under their firewall second node of the tree won't expand (will remain "Loading..."); from other locations the app works fine.
The client claims that FlyTree uses some other ports/protocols for callback other than port 80.
The question is if FlyTreeView can be configured to a specific ports so we can just do it for some specific port and ask the client to open it for us to experiment if this would solve the issue.
Link Posted: 29-Apr-2009 03:17
FlyTreeView uses same port and protocol that is used by page itself.
So it is port 80 by default. Nothing else just HTTP request to page (as it is a regular ASP.NET callback).
Link Posted: 29-Apr-2009 03:59
[quote="EvgenyT"]FlyTreeView uses same port and protocol that is used by page itself.
So it is port 80 by default. Nothing else just HTTP request to page (as it is a regular ASP.NET callback).


Is it any control in FlyTreeView component that allows to change the defaukt (port 80)?
Link Posted: 29-Apr-2009 04:03
If page URL is http://somehost/page.aspx
Then callback URL WILL BE http://somehost/page.aspx

If page URL is http://somehost:123/page.aspx
Then callback URL WILL BE http://somehost:123/page.aspx

For SSL:
if page URL is https://somehost/page.aspx
Then callback URL WILL BE https://somehost/page.aspx

FlyTreeView performs regular ASP.NET callbacks, they doesn't use any extra port