"Request Filtering" problems on a Shared IIS Host
We have a shared IIS hosted site on Network Solutions. One of our software products gets updates from files hosted by our website. Our software can access file extensions: .txt, .chm, .zip, .bin, etc., just fine. It is several other extensions that are giving a "404 File Not Found" error. (.ga, .os, .dll, .ceb)
Network Solutions support advised me to try to address the problem via IIS manager and connecting to the shared host. I have successfully done that. Under the Request Filtering section there are no outright blocks on any of the file extensions that i listed. I was able to add "Allow File Name Ext" rules for our 4 problem extensions. I confirmed that these changes persisted after coming back to the site through IIS Manager. I also recycled the Application Pools through Network Solutions. Note: These changes were implemented last week so should have had time to propagate.
After all of that the extensions in question still will not download. Any ideas? I was hoping to tackle this issue through IIS before enabling Directory View on the problematic folders.
The NetSol guys seem to be Unix hosted fanboys and have limited knowledge of IIS. Or at least they are hesitant to support IIS. I could care less about which is better arguments. I am faced with the reality that our site had loads of compatibility issues when it was temporarily Unix hosted and now it has less.
Network Solutions support advised me to try to address the problem via IIS manager and connecting to the shared host. I have successfully done that. Under the Request Filtering section there are no outright blocks on any of the file extensions that i listed. I was able to add "Allow File Name Ext" rules for our 4 problem extensions. I confirmed that these changes persisted after coming back to the site through IIS Manager. I also recycled the Application Pools through Network Solutions. Note: These changes were implemented last week so should have had time to propagate.
After all of that the extensions in question still will not download. Any ideas? I was hoping to tackle this issue through IIS before enabling Directory View on the problematic folders.
The NetSol guys seem to be Unix hosted fanboys and have limited knowledge of IIS. Or at least they are hesitant to support IIS. I could care less about which is better arguments. I am faced with the reality that our site had loads of compatibility issues when it was temporarily Unix hosted and now it has less.
Who is Participating?
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
