Questions[isapi-rewrite](server)

How do I need to change this rule for IIS to support all variations of domain.

I want all traffic to go to https://domaindotcom/folder/<personalisedID> - we have sent a letter to ask recipients to go to domaindotcom/<personalisedid>. Therefore need this to redirect automatically to where these pages are actually located which is https://domaindotcom/folder/<personalisedID>.

This is what I have so far, but this doesn't cover all variations that a user could enter into their browser.

i.e. www.domaindotcom, domaindotcom, https://domaindotcom, http://domaindotcom

All advice would be greatly appreciated, I'm very new to all this so very much stabbing in the dark!

#Redirect non-HTTPS to HTTPS 
RewriteCond %{HTTP:Host} domaindotcom [NC] 
RewriteCond %{HTTPS} off 
RewriteCond %{REQUEST_URI} (.*) 
RewriteRule .? https://domaindotcom/folder%1 [R,L]

In my httpd.ini I redirect all traffic from "example.co.uk" to "www.example.co.uk", the below works fine for this:

RewriteCond %HTTPS off 
RewriteCond Host: (?!^www.example.co.uk)(.+) 
RewriteRule /(.*) http\://www.example.co.uk/$2 [I,RP]

I have a bunch of microsites which also use this website, say "www.foobar.co.uk", set in the Host Headers of IIS 6. With the above rules, "www.foobar.co.uk" ends up at "www.example.co.uk"!

Is there a RewriteCond I can do against the request to make sure that the request is for "example.co.uk" to not capture the microsites and rewrite those? Or even better, a way I can take any request, be it "example.co.uk" or "foobar.co.uk" and just wack a www in front of it?

Thanks for your help.

Is there any way to configure IIS 7.5 to perform URL rewrites to different application pools on the same site without running into a 403.18 error?

We're using Helicon ISAPI Rewrite 3 on IIS 6 and it's working like a charm. The root-level "application" is running under it's own application pool, and on IIS 6 we have no problems doing URL rewrites from that application pool to any one of the other four application pools. But when I copy the same server configuration information over to IIS 7.5 the URL rewrites to any of the other application pools fail with a "403.18 -- Forbidden" error.

The weird bit is that the IIS 6 is not (at least as far as I can tell, by looking at the site Service configuration dialog) running under IIS 5 emulation mode, so somehow the rewrites aren't throwing 403.18 errors. So something must be different... but whatever it is, I sure haven't been able to figure it out.

Btw, we're not married to Helicon ISAPI Rewrite. If there's another way to preserve our current rewrite configuration rules using another module or method I'd be more than happy to use it.

I need a javascript form filler that can bypass the 'same origin policy' most modern browsers implement.

I made a script that opens the desired website/form in a new browser. With the handler, returned by the window.open method, I want to retrieve the inputs with theWindowHandler.document.getElementById('inputx') and fill them (access denied).

Is it possible to solve this problem by using Isapi Rewrite (official site) in IIS 6 acting like a reverse proxy? If so, how would I configure the reverse proxy?

This is how far I got:

RewriteEngine on
RewriteLogLevel 9
LogLevel debug 

RewriteRule CarChecker https://the.actualcarchecker.com/CheckCar.aspx$1 [NC,P]

The rewrite works, http://ourcompany.com/ourapplication/CarChecker, as evident in the logging. From within our companysite I can run the carchecker as if it was in our own domain. Except, the 'same origin policy' is still in force.

Regards,

Michel

I have IIS 6.0 and am using a ISAPI rewrite to do a special URL redirect.

Basically how this will function, anyone going to www.website1.com is redirected to www.website2.com which I have setup with the following lines:

RewriteCond %{HTTP:Host} ^website1\.com$
RewriteRule (.*) http\://www\.website2\.com [NC,R=301]

However, there are 2 URL's that I want exluded from the rewrite rule:
- www.website1.com\Mar\healthcheck.html
- www.website1.com\Mar\servname.html

What would I add to my current config for it to allow people through to those two URL's? Ideally it would just allow anyone going to www.website1.com\Mar\* through.

Thanks