Click here to Skip to main content
15,885,925 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
I have an asp.net page within which I've used several AJAX controls doing partial postbacks with update panels. In testing it works wonderfully, all of the postbacks are done without reloading the page and it makes the whole process smooth. I uploaded this to the web server for some outside testing and all of the tested reported that the page was reloading a lot. I tried it within the network from the web server and it was still working fine. However, when I tried it from outside the network at home, it does in fact appear to be doing full postbacks whenever it's set to do partial postbacks for these update panels.

I can't seem to find out why this is happening. Even with the increased time it takes to communicate with the server, it shouldn't reload the page - it should just, at most, stall for a moment. Another strange thing is that it's not maintaining the scroll position even though I have it set to do so for the one or two full postbacks I have. It reloads to the top of the page.

I'm thinking perhaps this may be something set on the server, but I can't be sure. Does anyone have any ideas?

Thank you
Posted
Comments
virang_21 12-Jan-12 4:28am    
Are you using the same browser outside too ? Is the external application hosted on different server ? If so check Ajax tool kit is installed on that server .. I am assuming that u r using AjaxControlToolkit here ..
Rlife 12-Jan-12 11:18am    
Yes I'm using the AjaxControlToolkit. When I access the application from the webserver internally, I am using a local route, but it's still on the same server. I'll have to check for the AJAX toolkit though.
That's Aragon 12-Jan-12 4:28am    
Verify the AJAX framework installed at the server with your local one. It may possible that both the version are mismatched. Are you getting any issue in page ? Like any java script error ?
Rlife 12-Jan-12 11:17am    
No there aren't any errors. I will have to check the AJAX version on the server though.
Rlife 19-Jan-12 12:33pm    
There were errors. I don't know how I missed that.

1 solution

It turns out the AJAX wasn't being loaded because the axd files were being filtered by the firewall of our network for having a URL that was too many characters. It was a tough find because there are a great deal of reasons why AJAX might not be loaded.
 
Share this answer
 
v2
Comments
fjdiewornncalwe 19-Jan-12 11:55am    
Thanks for providing the solution.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900