IIS 7 Rewrite to another application pool

Question

There are many related topics saying that you cannot rewrite an incoming request to another application pool in IIS 7 (one such post is https://serverfault.com/questions/220007/iis-7-5-multiple-application-pools- and-url-rewriting-403-18-forbidden ). Redirects will work, but the requirement for this project is that we cannot allow the user to see or search engines index the redirected Url.

So the question is: is there any other mechanism on the local server that allows you to intercept the request before IIS can start processing the request; somewhat reminiscent of old ISAPI filters. Many articles suggest using some form of Http Proxy or Software Load Balancer; both options are valid, but can cause some overhead of physical and virtual resources. Recall that the main goal is that we try to receive requests coming from the site www.domain.com/(.*) to be rewritten to www.domain.com/{currentversionasket/{R:1}, where the root website The website and the web application with the version are isolated from each other.

Answer 1

I may not understand you; but do you want essentially a reverse proxy? A way to rewrite the URL to avoid searching; where the client generates page resources, as if it came from the server. What can be used from the IIS Rewrite Module .

However, you can simply create two completely separate sites. Example:

• http://www.foo.com
• http://www.foo.com/en
• https://www.foo.com/en <- Logging in as if you are switching to https .

Thus, <sites> point to separate directories, then both are treated as separate objects, so you can create blocked responses on this page so that they are not found in the search engine.

If my answer is off; let me know and i will delete it. But I think this should work; in theory anyway. Squid and Varnish are also applications that were used to create reverse proxies .