Free domain Included free domain extensions:. Users receive data from the closest server, and get faster loading times as a result. Helpful advice from a single point of contact. Exclusively for you. Experience customer service on a whole new plane. All this and more, free.
|Published (Last):||27 December 2008|
|PDF File Size:||19.8 Mb|
|ePub File Size:||12.95 Mb|
|Price:||Free* [*Free Regsitration Required]|
If you ever wanted to change your web site's URL scheme, this product is for you! It uses intelligent configuration cache mechanism. All work is done just in one stage and there are no recursively requests or any other operations that may take a long time. It can serve as many sites as you have. With regular expressions you don't need to write a thousands check strings. The comparison and replace of URLs can be done with a few string patterns. See examples section for more information.
It supports virtually unlimited number of the rules and an unlimited number of attached rule conditions to provide a really flexible and powerful URL manipulation mechanism Really a config file size is forcibly limited to 2Mb to prevent possible config parsing overhead. The result of operation can lead to rewriting, proxiing, redirection, or blocking of the original request. The rewriting engine goes through the ruleset rule by rule RewriteRule directives. The particular rule is applied only if it matches against URI and all corresponding conditions RewriteCond directives matches against theirs test strings.
It means that pattern expression is NOT searched in the string, it is matched against the whole input string. Result of a successful rule application is saved in the original header and it will be visible for the subsequent rules. Rules processing stops when a last rule redirect, proxy, forbid or rule marked by the L flag is matched.
Rewriting will cause server to continue request processing with new URI as if it has been the originally requested by a client. New URI can include query string section following question mark and may direct to any files, script calls, program invocations etc. Proxiing causes the resulting URI to be internally treated as a proxy request and immediately i.
You have to make sure that the substitution string is a valid URI including protocol, host, etc. Redirection will cause server to send immediate response to a client with a redirect instruction HTTP response code with Location header , providing resulting URI as a new location. You can use absolute links that is required by RFC in a redirection instruction to redirect a request to a different host, port and protocol.
Redirect instruction always causes rewriting engine to stop rules sequence processing. Rules are processed in the order of appearance in a configuration file.
There are no recursive requests or subsequent rollbacks in a processing order except explicitly generated loops , so you will never get into an infinite loop. Then it can be retrieved in ASP using Request. These references are global for the entire RewriteRule directive and corresponding RewriteCond directives. Submatches are numbered from up to down and from left to right beginning with the first RewriteCond directive if such directive exists corresponding to the RewriteRule.
To simplify rules and strengthen server security it is strongly recommended to disable parent paths in the IIS settings. No other manual steps required to complete installation. Although some additional manual steps like file system permissions configuration or registration of the proxy in IIS script maps may be required.
You will need to download distinct manual installation package containing all required files. You could install all features or only a part of them. Minimal installation includes only the filter. Filter will try to load main configuration file httpd. Site level configurations are loaded from web site roots.
This could be done by launching provided regmsg. To enable monitoring of a site root path changes register COM server mtbnotif. On the Windows Server you should place file rwhelper. Do not install manifest file on other OSes. Configuration of the proxy module is described in the Configuration Utility section of this manual. But Lite version does not support per-site configurations and all relative features.
Only global rules are processed. In addition Lite version does not include proxiing engine. The following flags is not supported in the Lite version: P - proxy. In the WPI mode virtual web sites or even individual web applications are running inside Application Pools.
And each application pool is served by one or more isolated worker processes w3wp. It looks like High isolation mode in the IIS5 but there exists one significant difference. Filters are not running inside the inetinfo. They are running inside worker processes as usual applications. It means that there could be multiple instances of a single filter one instance for each worker process. Only redirect or proxy could be safely used in this case. We also recommend to give System account Modify permissions on all folders containing httpd.
That will allow creation of httpd. Additional permissions may be required for the proxy module. Since it could be running in the Pooled or High-isolated application modes, accounts of the IIS shared pool and high isolation pools should be given Read permissions to the rwhelper. By default w3wp process runs under the "Network Service" account. But since worker process account could be changed it would be better to find real process account in the application pool settings with the help of IIS MMC snap-in.
We also recommend to give those accounts Modify permissions on the directories containing httpd. There are two types of configuration files - global server-level and individual site-level files. The global configuration file should be named httpd.
The shortcut of this file is provided through the start menu. The individual configuration files should be named httpd. Both file types formats are the same and it is the standard Windows INI file braked by sections. All directives should be placed in this section and each directive should be placed on a separate line. Any text outside this section will be ignored. The RewriteCond directive defines a rule condition.
The following rule applied only if its pattern matches the current state of the URI and if these additional conditions apply too. Normalization includes removing of an URL-encoding, illegal characters, etc. The RewriteRule directive is the real rewriting workhorse. The directive can occur more than once. Each directive defines one single rewriting rule.
The definition order of these rules is important , because this order is used when applying the rules at run-time. Specifies regular expression that will be matched against Request-URI. See regular expression syntax section for more information.
Specifies format string that will generate new URI. See format string syntax section for more information. Flags is a comma-separated list of the following flags: I i gnore case Indicates that characters are matched regardless of case. This flag affects RewriteRule directive and all corresponding RewriteCond directives. Stops the rewriting process and sends Forbidden response to a client.
Note that FormatString is useless in this case and could be set to any non-empty string. Stop the rewriting process here and don't apply any more rewriting rules. Use this flag to prevent the currently rewritten URI from being rewritten further by following rules. Forces rewriting engine to modify rule's target and restart rules checking from the beginning all modifications are saved.
Number of restarts is limited by the value specified in the RepeatLimit directive. If this number is exceeded N flag will be simply ignored. Works like the N flag but restarts rules processing from the same rule i.
Maximum number of a single rule iterations is given by the RepeatLimit directive. But a number of a single rule repeats does not count for the global number of repeats i. Forces the result URI to be internally forced as a proxy request and immediately i.
You have to make sure that the substitution string is a valid URI including protocol, host etc. Force server to send immediate response to client with redirect instruction, providing result URI as a new location.
Redirect rule is always the last rule. Almost the same as the [R] flag but issues moved permanently HTTP status code instead of moved temporary. Normalizes string before processing. This directive can be used to rewrite, create or delete any HTTP headers, or even change method of the client request. Specifies a HTTP header that will be rewritten. Possible values are the same as for the TestVerb parameter in the RewriteCond directive.
Specifies regular expression that will be matched against specified header. Specifies format string that will generate new header value. This flag affects RewriteHeader directive and all corresponding RewriteCond directives.
Nos Types D'Hébergements
Software versions installed on Hosting accounts
Hébergement sous Windows