Yes, all our servers have the mod_rewrite module installed, so you should be able to modify your .htaccess files to rewrite URLs.

IIS Mod-Rewrite is compatible with apache mod_rewrite both in syntax and functionality. This means that a rewrite configuration for Apache is not only accepted by IIS Mod-Rewrite, but it also behaves the way Apache mod_rewrite does. However, some of the functions available in apache mod_rewrite are not implemented in IIS Mod-Rewrite, simply because IIS and Apache have completely different design and those functions are meaningless for IIS.

There is an article from Ralf S. Engelschall about URL-manipulations based on mod_rewrite in the "iX Multiuser Multitasking Magazin" issue #12/96. The German (original) version can be read online at <http://www.heise.de/ix/artikel/1996/12/149/>, the English (translated) version can be found at <http://www.heise.de/ix/artikel/E/1996/12/149/>.

Hmmm... there are a lot of reasons. First, mod_rewrite itself is a powerful module which can help you in really all aspects of URL rewriting, so it can be no trivial module per definition. To accomplish its hard job it uses software leverage and makes use of a powerful regular expression library by Henry Spencer which is an integral part of Apache since its version 1.2. And regular expressions itself can be difficult to newbies, while providing the most flexible power to the advanced hacker.

You can't! The reasons are: first, that, case translations for arbitrary length URLs cannot be done via regex patterns and corresponding substitutions. One needs a per-character pattern like the sed/Perl tr|..|..| feature. Second, just making URLs always upper or lower case does not solve the whole problem of case-INSENSITIVE URLs, because URLs actually have to be rewritten to the correct case-variant for the file residing on the filesystem in order to allow Apache to access the file.

If the rule starts with /somedir/... make sure that really no /somedir exists on the filesystem if you don't want to lead the URL to match this directory, i.e., there must be no root directory named somedir on the filesystem. Because if there is such a directory, the URL will not get prefixed with DocumentRoot. This behavior looks ugly, but is really important for some other aspects of URL rewriting.

Author: Alex Chaffee (http://www.jguru.com/guru/viewbio.jsp?EID=3) You have to add the '--enable-module=so' option to your 'configure' call in order to enable DSO, i.e.: ./configure --prefix=/usr/local/apache --enable_rule=SHARED_CORE --enable-module=so (Thanks to Peter Theill from the Tomcat User Mailing List.) Comments and alternative answers

Apache has been shown to be substantially faster, more stable, and more feature-full than many other web servers. Although certain commercial servers have claimed to surpass Apache's speed (it has not been demonstrated that any of these "benchmarks" are a good way of measuring WWW server speed at any rate), we feel that it is better to have a mostly-fast free server than an extremely-fast server that costs thousands of dollars.

The module currently supports iPlanet Enterprise Web Server 4.1 and Sun ONE Web Server 6.0. Netscape/iPlanet FastTrack Web Server is currently unsupported.

If the index page shows up then you got mod_rewrite. if you're on a Windows server, it probably won't work. Right after RewriteRule ^ enter the static URL, then a $, a space, and then original URL (with out the http://www.domain.com part for both URLs). RewriteRule ^store/Nintendo/4867635/Pokemon.html$ cgi-bin/store.cgi?section=Nintendo&id=4867635&item=Pokemon In the first URL, the static URL code, where ever the URL will change, replace it with a [^.

To activate IIS Mod-Rewrite you must first purchase a license key. You can buy a license key online from micronovae.com After you have received the license key, open IIS Mod-Rewrite Control Center from your Start menu, and select the "Activation" tab. You simply have to type the license key and click the "Activate" button to activate IIS Mod-Rewrite.

If you get "404 - Page Not Found" errors and images that don't show up, you probably have told zenphoto to use mod_rewrite, but you don't have it enabled on your server. You should set the configuration option 'mod_rewrite' to false. In zen/zp-config.php, edit the line $conf['mod_rewrite'] to read: $conf['mod_rewrite'] = false; Reset this option from the admin options/gallery configuration tab. Or you can read the next question to see how to turn it on. You will need to open up the .

mod_rewrite is an Apache module, so it requires Apache. If you're on a shared web host, you'll have to e-mail them and ask for it. Most large web hosts that use Apache will have it enabled already, but yours may not, it's not uncommon. Secondly, you need to edit the .htaccess file in your zenphoto installation and make sure the RewriteBase line is correct. It should be the URL to your zenphoto after the domain name. For example, the RewriteBase for http://www.zenphoto.

Yes, mod_rewrite is standard on our servers and is available to everyone. See the Apache mod_rewrite documentation for more information. mod_rewrite users may also find the following cheat sheet handy. As always, don't hesitate to contact us if you need help with this feature.

The most frequent reasons that IIS Mod-Rewrite may not work or may seem not to work are the following three: You may have not activated IIS Mod-Rewrite. In such case, IIS Mod-Rewrite stops working after 30 minutes or after 1000 request, whichever is reached first. You need to restart IIS to get IIS Mod-Rewrite back working for another 30 minutes or 1000 requests. Your configuration script may have errors, or the regular expressions in it may be misconfigured, thus not working as you want.

Because all of our applets run on your visitor's browser, we do not require any special web-server processing or installation. That makes us compatible with virtually every web server in use today. This includes Apache, Microsoft -IIS, Netscape-Enterprise, Zeus, Rapidsite, thttpd, Tiger Shark and almost any other HTTP server on virtually any platform. Our calculators have been successfully setup on Windows 2000, Windows XP, Windows Vista, Mac OS X, Linux and Unix.

runs on Windows NT/9x, Netware 5.x and above, OS/2, and most versions of Unix, as well as several other operating systems DBM databases for authentication allows you to easily set up password-protected pages with enormous numbers of authorized users, without bogging down the server. Customized responses to errors and problems Allows you to set up files, or even CGI scripts, which are returned by the server in response to errors and problems, e.g.

Absolutely. Set up a configuration file with your vhost information in it and point logmonster at it. The format for each vhost is as follows: <VirtualHost> ServerName www.tnpi.net ServerAlias www.thenetworkpeople.net *.tnpi.net DocumentRoot /home/tnpi.net/html </VirtualHost> Create as many vhost directives as you need and logmonster will parse them all. When you make changes to your web server, update this file as well. All the other rules apply equally.

A compiled mod_jk for linux can be found at http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.1/bin/linux/i386/ , documentation at http://jakarta.apache.org/tomcat/jakarta-tomcat/src/doc/mod_jk-howto.html No, mod_jk and mod_jserv are not compatible (cannot be installed in the same instance of Apache). When transitioning, I've used mod_jserv for both Tomcat and JServ instances with different ports.

quot;Writing Apache Modules with Perl and C", by Stein and MacEachern, O'Reilly and Associates Inc.

See "HP Apache-based Web Server Migration Guide, Version 1.3.x to 2.x" www.hp.com/products2/unix/webservers/apache/techtips/index.html.

Permalinks are the permanent URLs to your individual weblog posts, as well as categories and other lists of weblog postings. A permalink is what another weblogger will use to refer to your article (or section), or how you might send a link to your story in an e-mail message. By default, Wordpress permalinks will look like this: http://yourdomain.com/index.php?p=1. The “p=1″ part of this example URL refers to a blog post (”p”) with an ID of “1″.

IIS Mod-Rewrite Pro supports all the features of Standard version, and additionally supports per-directory and override configurations.

IIS Mod-Rewrite Standard is designed for Windows Server 2000 and Windows Server 2003. It is also successfully tested on Windows XP Pro, Windows Vista and Windows Longhorn Server, but it is not recommended to be used on any other operating system than Windows 2000/2003 Server. IIS Mod-Rewrite Pro is designed only for Windows Server 2003.