Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By icame on
Already stated my problem here:
I used this guide:
http://www.iis-aid.com/articles/how_to_guides/using_drupal_clean_urls_wi...
Need someone to go over step by step over gmail chat to get it to work, name your price please, per hour will work too with limit of one hour.
I'm using the Isapi Rewrite, full edition.
Comments
Wrong tool
You are using the wrong tool. ISAPI Rewrite is known for the headaches it gives you when trying to port rewrite configurations from apache...
Sorry if I'm telling you this too late, but you should have used IIS Mod-Rewrite Pro. It's compatible with Apache mod_rewrite and you can use the .htaccess shipped with Drupal (remove only the <ifmodule mod_rewrite.c> tag)
I have to disagree with that
I have to disagree with that first statement. Although perhaps not as straight forward as something like IIS Mod-Rewrite Pro in translating Apache mod_rewrite rules, ISAPI Rewrite is a very capable product which I've been able to fairly eaily able to adapt to rewrite rules for Drupal, Wordpress and Gallery 2 (which actually creates the rules for ISAPI Rewrite for you). There should be no reason why you can't follow the guide I wrote above and have ISAPI Rewrite working for you. If there are any things that you are unsure of with the guide, let me know so I can help you out and update the guide for future users.
----------------
Dominic Ryan
www.iis-aid.com
Dominic, there is nothing
Dominic, there is nothing wrong with your article. But there are many things that are wrong with ISAPI rewrite. As a matter of fact, the company is moving to a new version that claims it'll work the same way as IIS Mod-Rewrite. In my opinion it's too late for them as IIS Mod-Rewrite is a lot more stabile and better integrated. But it's good news anyway as the aparent competition between these two products will bring us better solutions :-)
Could you be more specific
Could you be more specific with what exactly you think is wrong with ISAPI Rewrite? If it is simply that Apache Mod Rewrite rules are not directly transferable to it then that is hardly something wrong, that is because they are different products. Can you also expand on why you think ISAPI rewrite is not stable? ISAPI Rewrite has been around since early 2002 (over 5 years) and I've used it for years and have seen it used in some rather large and complex IIS environments where I would be very, very surprised to see it being used if there were any question regarding its stability. One thing I can agree on though is that with other rewriting tools for IIS popping up now we should see a richer feature set and more competitive pricing.
----------------
Dominic Ryan
www.iis-aid.com
I'll also give support to ISAPI Rewrite
ISAPI Rewrite may not be 100% compatible with existing mod_rewrite cookbook solutions but it is an excellent product and I have used it successfully for several websites where at least one was high traffic.
Wrong
Brashquido, ISAPI Rewrite clearly intends to be a mod_rewrite port for IIS (this is what the company claims anyway), but unfortunatelly it's loosely compatible. It's a good and capable tool, but it works the way it wants, not the way I want. Not the standard mod_rewrite way. This is what I consider as very wrong, in particular when I compare it with IIS Mod-Rewrite which is 100% compatible, it's quite stable too, and works a lot better for me.
Sorry, I wasn't clear about stability. I was talking about the new version 3 of ISAPI Rewrite which is very bad for the moment. The old version 2 has proven quite stabile as long as I have used it in the past.
Also, may it's just the way I see things, but you pinched a sensitive nerve of mine. After 5 whole years the ISAPI Rewrite team has done absolutely nothing regarding mod_rewrite compatibility. But after IIS Mod-rewrite emerged, they immediately started pushing a partially and badly implemented compatible beta version (v3) - I'm sure these two events are related. It's very disappointing to see a dominating product or company falling back.
Blur, I think you'll find
Blur, I think you'll find that ISAPI Rewrite was originally developed simply as a URL manipulation tool for IIS with little or no intention for Apache mod_rewrite rules to be directly transferable. Their site states that it acts like mod_rewrite (i.e URL manipulation), and with the exception of Beta 3 no where that I can see makes any claims that rules should be directly transferable from mod_rewrite. Also, what makes mod_rewrite the official standard? Are there any RFC's etc that state all URL manipulation tools regardless of webserver platform should use the rule syntax that mod_rewrite is using? I seriously doubt there ever would be as there are several mod rewrite directives that are bound specifically to the Apache architecture, such as subrequests which IIS does not use at all (and therefore no IIS based URL manipulation tool is ever going to support). I was using ISAPI Rewrite to manipulate asp based URL's back in 2003 when ISAPI Rewrite was already nearly a few years old and long before PHP on IIS became anything near mainstream. With that in mind I don't see how you can possibly claim that ISAPI Rewrite was intended simply as a mod rewrite port for IIS. Bottom line is that the only thing really driving demand for mod rewrite compatible rules for IIS URL manipulation tools is the popularity PHP has gained as a language on the IIS platform over the last few years.
If the only URL manipulation you will be needing on your IIS platform is to transfer mod rewrite rules for PHP apps then at present I would have to agree that IIS Mod Rewrite Pro looks like one of the better choices, and certainly better than ISAPI Rewrite in it's present form if you are not familiar with rule creation at all. However in no way is ISAPI Rewrite the wrong tool for the job either, and in a very long winded nutshell that was really the only point I was trying to make.
----------------
Dominic Ryan
www.iis-aid.com
Double post apologies
Double post apologies. Clicking submit refreshed the page but without my post....
Uh, v3 is still BETA, what do you expect?
That's a rather high bar to reach, don't you think? I mean, if everyone said that "there are many things wrong with" products that didn't think work they each wanted then all products would be inappropriately getting really bad press.
What's more, the v3 is in beta which means nobody should expect it to be perfect yet, ferchrisakes! It is rather intellectually dishonest to bash a product in a public forum for the quality of its beta version without stating that is was the beta version being bashed, don't you think?
You don't just happen to be part of the company that sells IIS Mod-Rewrite Pro, are you? Sorry to imply if you are not, but happens too often that vendors of new products anonomously bash their competitiors on public forums.
If they had promoted absolute mod_rewrite compatibility in the past it would be one thing. Frankly I think they have been shortsighted not to include mod_rewrite compatibility and several other things I'd asked for which they ignored, but it's their product and they get to choose what they include and what they don't. And as long as they don't misrepresent it, then it's all fair.
FWIW, I finally gave up on Windows & IIS for web serving and am on to Apache and open source, and not looking back...
Sadly, your implications
Sadly, your implications ruin this very nice discussion...
Just because I see this discussion is getting badly derailed, initially, I just wanted to suggest a simple and working solution to this poor guy "icame". Later on, this turned to a nice discussion with "brashquido" and all I wanted to say is this: when looking for optimal solutions I just prefer to choose technologies that work better for me and look to be ahead compare to others. Pretty much as for aparent reasons drupal, as of version 5, is one of my two favorite cms solutions compare to hundreds of others... (sorry, but it's not the right forum to say which is my other favorite one ;-)
That's all!
Implications come from you as well
@blur: Sadly, your implications ruin this very nice discussion...
And I felt the same of your implications, which is why I spoke up. I know how hard it is to be a vendor selling to developers so when I see someone inappropriately disparaged, I speak up.
Very useful
Check also this solution article. Very useful, and it works perfect!!
Clean Permalinks for IIS using .htaccess
Thank you! Going to see if I
Thank you! Going to see if I can get my money back because isapi rewrite didn't work at all for me and I followed all directions and double checked as well to make sure. Will try out this product instead.
icame, if you don't manage
icame, if you don't manage to get your money back for ISAPI Rewrite I'll be happy to assist you in getting it to work for you.
----------------
Dominic Ryan
www.iis-aid.com
Triple post apologies.
Triple post apologies. Clicking submit refreshed the page but without my post....
Triple post apologies
Triple post apologies. Clicking submit refreshed the page but without my post....
Triple post apologies
Triple post apologies. Clicking submit refreshed the page but without my post....
WOW! Didn't notice so many
WOW! Didn't notice so many replies. Actually got the program to work, it took a while and some $$ but a programmer did fix everything for us to make it functional and working. Not sure what he did but it works like a gem.
Thank you everyone for posting, and sorry for not replying earlier.
Drupal module, imagecache, I
Drupal module, imagecache, I did not realize is relying on a mod_rewrite trick for the "caching" functionality. It relies on the -f flag which tells mod_rewrite to ignore the rule if the file already exists (a jpg image generated by GD in the case of the imagecache module). ISAPI_rewrite from Helicon, at least in it's 2.x incarnations, does not support the -f flag. IIS mod-rewrite from Micronovae does supposedly support the flag, but I cannot get it to recognize per-directory .htaccess files for some reason. It seems to be working with the default configuration settings however, but I'll be contacting their support for help and hopefully get this solved before I spend the cash for the license and report back here with my results. Hopefully Helicon will get version 3 stable and affordable ... but I'm not holding my horses.
Please realize that Dominic's guide for Helicon's ISAPI_rewrite is great and has served us well for a long while, but I am finding that it simply will not support the imagecache module in its current state. It is always possible that I am overlooking some other great free product or that I should give up on IIS entirely and finally and migrate to Apache, but please do let me know if I am missing something obvious or important.
I should have replied
I should have replied sooner, as Helicon's ISAPI_rewrite 3 appears to have improved greatly, adding support for virtually all Apache style mod_rewrite rules, the useful ones anyway. I will try to summarize simply with a list of pros/cons contrasting these two vital applications.
Helicon's ISAPI_rewrite 3 for IIS
Pros
Cons
MicroNovae's mod_rewrite for IIS
Pros
Cons
In summary, I personally prefer using Helicon's paid-version. I would prefer modifying settings.php in a over altering every .htaccess file the way MicroNovae seems to prefer. I also like Helicon's GUI hooks for IIS Admin.
While Dominic's guide for Helicon's Lite version was very useful, I finally found it much less headache to pay the $99 to upgrade to the full 3.x version. For those who still use the Lite version, here is Dominic's new guide to upgrade your 2.x rules to work for 3.x http://www.iis-aid.com/articles/how_to_guides/using_drupal_clean_urls_wi.... This should bring everyone up to free rewrite support for imagecache module.
Correction
Webavant,
I must correct you. It is ISAPI_Rewrite that requires trimming the .htaccess file down to only mod_rewrite rules. IIS Mod-Rewrite seems to ignore non-mod_rewrite stuff and only needs to comment out the <IfModule mod_rewrite.c> to work. ISAPI_Rewrite will complain on everything that is non-mod_rewrite.
I also ran into this post that reports some serious incompatibility issues with ISAPI_Rewrite, which appear to be true as I tested and confirmed all of them. This is yet another big reason to stick with IIS Mod-Rewrite if choosing to pay. Also, IIS Mod-Rewrite supports more RewriteMap functions dbm: and prg: (however those would hardly be used in Drupal setups). In general IIS Mod-Rewrite looks to be a complete and accurate port of mod_rewrite. ISAPI_Rewrite looks to have many compatibility holes.
I must mention though that ISAPI_Rewrite 3 has GREAT improvements compare to v2, and those who like to stick with ISAPI_Rewrite should upgrade to v3.
The only think I like more in ISAPI_Rewrite 3 is that you can edit .htaccess files in ISAPI_Rewrite Manager and IIS Manager. Really cool feature, but it's the last thing I would consider to choose a product.