Hey there,
First thing's first - if this is posted in the wrong forum, I apologize. Next...
I've got an ASP.NET AJAX application developed with VS 2008 Beta 2, using the 3.5 version of the Ajax Control Toolkit - when deploying it to our web server, something interesting happens. If I access the site through a machine on the same network as the web server, it renders fine. However, if I access it from another network, or through the internet, the TabContainer is not rendering.
I checked out the reason why, and it appears that our firewall is blocking the client's ability to download the WebResource.axd file associates with the Ajax Control Toolkit - what else is interesting is that I'm also using FreeTexBox on this page (which downloads a seperate WebResource.axd file, and can access it without any problem).
If anyone has any suggestions, or has run into this problem in the past, please let me know. Thank you!
Anthony
32 views and no responses?
Wow...either I didn't explain it well enough, or nobody's run in to this.
Can anyone let me know which is the case?
Thanks.
Well, if you want comments, here is mine.. I always read anything related to the tabs since I use them a lot...
But sorry, never run into this, works fine on my laptop and the corporate machines (that have high security)... And firefox, ie 6-7...
- Have you tried with another machine, that is not on same network as webserver + where you can test different firewalls/settings?
- Also, are you sure the tabs are to blame? Is everything on your web app from the same domain?
It could be so many different things...
Yeah I had a similar issue. We use an Aventail product (now SonicWall I believe) to allow users to login securely to our network over the net. It was configured in a way that was stopping that WebResource.axd file from being downloaded.
It seems that the issue is with your firewall. If it is blocking the file then there is little you can do. We configure our firewall\Aventail product to be a little less stringent so that the file is now downloaded and the asp.net ajax apps work fairly well. There are still other issues.
So I think you need to talk to your Network Admin people...?
Hi Anthony,
Why not use a debugging tool such as Web Development Helper,Fiddler and Firebug(used on Firefox) etc? They will help you on detecting all the downloaded items.
Best regards,
Jonathan
Jonathan Shen – MSFT:
Hi Anthony,
Why not use a debugging tool such as Web Development Helper,Fiddler and Firebug(used on Firefox) etc? They will help you on detecting all the downloaded items.
Best regards,
Jonathan
Thanks for the suggestion - that's the point of my query, however. I do in fact know that the file is not being downloaded, I'm just trying to determine what changed between the AJAX Toolkit for VS2005 and the toolkit that's compatible with 3.5 (VS 2008) that's causing it to be filtered by our firewall. It seems odd to me that it would work with a prior release, yet not with the new version.
After some more debugging, I think I may have determined the reason why the ScriptResource.axd files are not being downloaded - it appears that they are using a Content-Type of application/javascript, where WebResource.axd (downloaded without any problems) uses Content-Type application/x-javascript.
Additionally, I checked older projects built on VS 2005 .NET 3.0, and the ScriptResource.axd files there use Content-Type text/javascript.
So the question then becomes: Why in the world was the Content-Type changed to something which isn't successfully downloading?
Thoughts?
Alright, for anyone who searches this post in the future, here's the solution that we just implemented and tested:
First of all, we checked the content type of the files that weren't coming through to the client when it was posted to the web using Fiddler2 (http://www.fiddlertool.com/fiddler/).
When we checked the remote site, Fiddler showed that the files were forbidden. I checked it through localhost to see that the Content-Type was application/javascript.
Then, we checked our firewall. We had both application/x-javascript, and text/javascript, but no application/javascript!
We updated the configuration file for the firewall to include application/javascript content-types, uploaded it, and tested the site again - Voila, the Ajax Control Toolkit now works with Visual Studio 2008 and the 3.5 framework.
Thanks everyone for their help with this, much appreciated.
No comments:
Post a Comment