Forum Moderators: open
a) deal with it.
b) find another host.
you really can't argue with a webhost about installing ISAPI filters on their servers, even though nothing is affected accept the domain the filter is applied to. it's just one of those things i guess.
-Matt
I want to have a dedicated server to do what I want but I need sql. Now my host tells me that I have to have sql server on my machine and cannot access their mysql because of security reasons. Microsoft the nice people tell me a licence is 20,000 euro.
No wonder linux does so well
None of our ISP's want to put asp_rewrite on the servers.
They'll catch on sooner or later. Those that wait until later will be playing catchup after the fact. If a host is unwilling to implement ISAPI Rewrite filters, then you probably need to find a new host.
I've found that one of the reasons hosts don't want to install the rewrite engines is because they don't understand them. Another reason is that they require manpower and time to set up correctly and therefore would require additional costs. If you are working with a Cheap Host then I can understand why they don't want to implement the filters.
Another reason I've found is that few of them realize you can set up ISAPI Rewrite on unlimited virtual domains per server. This is a feature that is of utmost importance to those providing hosting services on shared IPs. Without the virtual domain support, I can see why they would want to avoid it.
It is hard to find a host that allows isapi filters. You should either deal with the work arounds like a smart 404, or find a host or dedicated server that will allow isapis.
You guys know of one?
Mac
With 24 hour support?
I think you are only going to get that with larger hosting operations.
When it comes to ISAPI Rewrite, the host drops a config file in the virtual directory. Once you've set up the config file, you usually don't need to touch it until additional expressions need to be added.
Based on experience, I can tell you that it takes many manhours to set up a config file for a site that could possibly serve over 400k pages from a database.
If it is a site that is currently live and has been for a while using unfriendly URIs, then add x amount of time for setting up 301s, 404s, etc. This is probably the main reason many don't want to deal with it. It can be very time consuming if you are not familiar with writing regular expressions and setting up 301s.
If it is a site that is new, whew, you've saved yourself a load of heartache and time. Starting from the beginning is the ultimate option and one that I highly recommend to anyone getting ready to launch a dynamically driven site.
Another time consuming process is planning the URI structure. Once the new rewritten URIs are in place, you don't want to have to go back and change them. Careful consideration needs to go into naming directories and files for maximum usability.
