Problem with cross-domain url?

2 posts, 0 answers
  1. dino
    dino avatar
    15 posts
    Member since:
    Jul 2012

    Posted 10 Sep 2012 Link to this post

    I'm attempting to use the tabcontrol/pageview combo to serve pages from a site on a different server (same network). It doesn't seem to work correctly in Google Chrome (ver 21.0.1180.89 m) or IE9 on win7.  I've tested in IE8 on windows server 2008 and it works.

    Now, the remote site is running a 3rd party application that runs in IIS and accesses data from our mainframe.  The page that serves up the responses from the application is a classic ASP page.  It's difficult for me to provide any more detail than that since I don't really know how it works.  But the behavior is this - the first "page" loads without a problem.  As soon as I try to navigate away from that entry page, I get a blank screen and the server hangs (the 3rd party server, not the web server).

    I think this is a shot in the dark here since it's a very unique situation and I doubt there will be anyone familiar with it exactly but I'm hoping someone has had similar issues with using the tab/pageview controls and may have run into similar problems and could offer me a few things to try.  I'm also going to contact the software vendor to see what they can tell me.  As far as I can tell, though, it's browser-related at least somewhat which leads me to believe it may have something to do with cross-site security.

    If you want more info, I can provide it.

    Thanks.
  2. dino
    dino avatar
    15 posts
    Member since:
    Jul 2012

    Posted 10 Sep 2012 Link to this post

    OK, I just realized something that kind of narrows it down a bit. Long story short, when I log in to my company network I'm logging in from a different domain. I believe this has more to do with the problem than the browser version. I often have trouble with permissions and security where others in the company do not because of this situation (it has to do with the fact that work from a laptop off site and log in through a VPN when I'm not at the office).  Needless to say, I think that means that the problem I'm experiencing is going to either go away once we have the site live or it will happen for everyone once the site it live.  I guess I need a public IP address to test it out.
  3. UI for ASP.NET Ajax is Ready for VS 2017
Back to Top