RewriteRule .? – [G]
<IIsFilter Location ="/LM/W3SVC/1800802984/filters/ISAPI_REWRITE"
FilterPath="C:\Program Files\Helicon\ISAPI_Rewrite3\ISAPI_Rewrite.dll"
>
</IIsFilter>
<IIsFilters Location ="/LM/W3SVC/Filters"
AdminACL="49634462f0000000a400000040000000b171b2f1d344c28255ce51e983b630fed611621d5ecedb78dbe4d4cf30d63e00bb48ac0f5f50c7ecafaf6a3bc3de47b88f801eff2a1c5deda33ad14d7970891db279691971967ed7214857d1b7393ed14cb23e0c248b389f1ad5ebd7b467ef0a0f510a4a967021f12c840c0097ca7e01c449811791c3abf7594c4a61b16498d62dd88d97ac2773ca613785a820f796656421ec2a2780f31897832216525befc0e505582a3377e9928d3ace3b5c59dc00020ee64908c1d1f355776fb12408b349f691ef5761086a5b81869459e2f34e03772da0fb49dc45b8c0d7c1c12c4a252d51e69ce79bb7342d"
FilterLoadOrder="ASP.NET_2.0.50727.0,ISAPI_Rewrite3"
>
</IIsFilters>
RewriteRule .? – [G]
Proxy-server is a network service empowering clients to perform indirect requests to other network services. Proxy-server may be considered an intermediary. The brief description of proxy-server operation is as follows:
And the client may be ignorant that the requested resource was delivered from another server.
HTTP-proxy is an implementation of proxy service for HTTP protocol. HTTP-proxy may be either reverse or forward.
Reverse HTTP-proxy usually lives between external network and internal network, it resolves external namespace into internal one, it is a barrier between external clients and live web-servers on the Intranet. The example is given below. Reverse HTTP-proxy is used to disguise internal network infrastructure, balance load among back-end servers, caching and HTTP responses compression. As a rule external clients have no idea that they are getting response from reverse proxy server.
Forward HTTP-proxy (aka Web-proxy) is used to reside between internal network and external network (Internet) and restrict access to specific HTTP resources, HTTP responses caching and web surfing. To make use of forward proxy the client shall explicitly specify its address (e.g. in browser settings). HTTP requests to forward proxy look like:GET http://example.com/ HTTP/1.1
Host: example.com
Accept: */*
User-Agent: MozillaNote! The peculiarity of forward proxy request in comparison with direct request is that the path after GET (and any other HTTP method) is a fully qualified URL (including protocol and host part) and not just the local path to destination (starting with /).
Helicon Ape owns a mod_proxy module that implements both reverse and forward proxy functionality. All basic aspects of this module along with examples may be found in the docs.
Forward proxy in Helicon Ape is enabled by ProxyRequests On directive. Before enabling you need to secure your server so that only authorized users could access the proxy.
Reverse proxy is enables by ProxyPass directive. For example:
ProxyPass /app/ http://backend.domain.com/or (the first parameter may be omitted when the directive is used inside <Location> section or .htaccess):
<Location /app/>
ProxyPass http://backend.domain.com/
</Location>The above config will proxy all requests starting with /app/ to backend.domain.com previously removing /app part from the path:
/app/item/33/ -> http://backend.domain.com/item/33/.
To make HTTP response headers change when reverse proxying (e.g. Location header upon redirect) ProxyPassReverse directive may be used, and to change domain names and paths in cookies the following directives are used: ProxyPassReverseCookieDomain and ProxyPassReverseCookiePath.
Now we'll illustrate you an example of non-trivial proxy application.
Given: front-end server example.com visible from external network.
Goal: Realize load balancing among three back-end application servers accounting for their performance and two back-end servers storing static files (images, CSS, etc.). Say, the second and the third back-end application servers are twice as productive as the first one, and the second back-end for static is thrice as powerful as the first one.
Solution. The reverse proxy configuration in httpd.conf will be:
<VirtualHost *:80>
ProxyPass /static/ balancer://cluster-static/ lbmethod=bytraffic
<Proxy balancer://cluster-static>
BalancerMember http://static1.example.com/ loadfactor=1
BalancerMember http://static2.example.com/ loadfactor=3
</Proxy>
ProxyPass / balancer://cluster-app/ lbmethod=byrequests
<Proxy balancer://cluster-app>
BalancerMember http://app1.example.com/ loadfactor=1
BalancerMember http://app2.example.com/ loadfactor=2
BalancerMember http://app3.example.com/ loadfactor=2
</Proxy>
</VirtualHost>The search of ProxyPass directive to match current request is performed subsequently, so directives with shorter matching patterns should be put lower in the config. balancer: protocol in ProxyPass directive tells that requests will be forwarded to the URLs specified in subsequent BalancerMember directives. lbmethod=byrequests parameter indicates that balancing will be based on the number of requests to back-end server; bytraffic value means that load balancing will depend on the quantity of bytes transmitted from back-end.
To accelerate your proxy-server responses from the back-end may be compressed and cached. To do that we add the following line into the VirtualHost section of our htpd.conf:
# enable compression
SetEnv gzip
# enable caching
CacheEnable mem http://app1.example.com/
CacheEnable mem http://app2.example.com/
CacheEnable mem http://app3.example.com/Please notice that caching will only work if the response from back-end contains expiration headers; e.g., Cache-Control: max-age=60.
As you could see Helicon Ape mod_proxy module possesses full-fledged proxy functionality to satisfy the most exacting needs.
Best wishes,index.php?id=123? Do you need to spend loads of hours tinkering with a source code? Definitely NO!
Right here we are going to show you an easy and powerful way to let SEO in your server without significant effort.
Luckily Helicon Ape
just got all needed features.
LoadModule linkfreeze_module modules/mod_linkfreeze.so linkfreeze filter. The easiest way is to write the following in httpd.conf:SetOutputFilter linkfreezeAddOutputFilter linkfreeze .phpLinkFreezeEngine onLinkFreezeEngine is switched on by default. However you may use this directive
to disable the module in specific context. For example you may use mod_linkfreeze for several locations only:LinkFreezeEngine Off
<Location /foo/>
LinkFreezeEngine on
...
</Location>
<Location /bar/>
LinkFreezeEngine on
...
</Location>LinkFreezeRule is the magic and power of mod_linkfreeze. This directive controls the whole process of «freezing».
Basic syntax is described in the documentation.
Let's see what happens if we try this:LinkFreezeEngine on
LinkFreezeRule --- php=html
LinkFreezeRule. Do you remember that dynamic links have three separators as usual? The first is a question mark (?) for query string separation, the second is ampersand (&) for query string arguments separation and the third is equality sign (=) which separates arguments names and their values. Three hyphens are needed exactly to replace these separators in the following order: ?&=. We decided to use hyphens but it wasn't necessary.php=html. Obviously it means extension replacing from ‘php’ to ‘html’. You might decide to
use something more funny:
LinkFreezeEngine on
LinkFreezeRule --- php=aspx
LinkFreezeRule supports optional flags.
MoveExt moves file extension and LowerCase casts a link into lower case. Let's try it:
LinkFreezeEngine on
LinkFreezeRule --- php=aspx [MoveExt, LowerCase]
LinkFreezeEngine on
LinkFreezeRule --- php=html [MoveExt, LowerCase, Params="u|g|f|p|mode|id|search_id"]
LinkFreezeEngine on
LinkFreezeRule --- php=html [Redirect, MoveExt, LowerCase, Params="u|g|f|p|mode|id|search_id"] |
 |
LinkFreezePageSizeLimit directive allows to restrict the maximum size of pages to process. mod_linkfreeze won't do anything
with the part of page exceeding the LinkFreezePageSizeLimit value. By the way Google also doesn't enjoy parsing huge pages till the end.
The value of directive should be specified in kilobytes:
LinkFreezePageSizeLimit 4096create database farcrydatabase;
C:\inetpub\wwwroot\farcry.
index.cfm?objectid=E689D722-06DF-6D24-56726E44740068B5. Not a friendly URL at all…
RewriteEngine On
RewriteCond %{REQUEST_URI} !(^/farcry|^/webtop|^/flex2gateway|^/flashservices|^/cfide)($|/)
RewriteRule ^([^.]+)$ index.cfm?furl=/$1 [L,NC,QSA]
Posts
All Comments
