Solved

"Request Filtering" problems on a Shared IIS Host

Posted on 2014-02-11
2
409 Views
Last Modified: 2014-02-25
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.
0
Comment
Question by:mcbathost
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 18

Accepted Solution

by:
Matthew Kelly earned 500 total points
ID: 39869152
Beyond the request filtering, IIS will not return a file type it doesn't know. See if those extensions are listed in the MIME types: http://technet.microsoft.com/en-us/library/cc725608(v=ws.10).aspx
0
 

Author Comment

by:mcbathost
ID: 39885786
We are learning that mot shared hosts, IIS or otherwise, will not let you add to a whitelist for proprietary or custom extensions.  So the option is to change our current naming conventions to make the server happy or move to a virtual host.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

As tax season makes its return, so does the increase in cyber crime and tax refund phishing that comes with it
This article was originally published on Monitis Blog, you can check it here . Today it’s fairly well known that high-performing websites and applications bring in more visitors, higher SEO, and ultimately more sales. By the same token, downtime…
Any person in technology especially those working for big companies should at least know about the basics of web accessibility. Believe it or not there are even laws in place that require businesses to provide such means for the disabled and aging p…
The viewer will get a basic understanding of what section 508 compliance can entail, learn about skip navigation links, alt text, transcripts, and font size controls.

738 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question