bopapa_1979's questions

We have a situation where we would like to redirect https://service1.domain.com to https://service2.domain.com. I know this is very simple with http endpoints, but I'm not too sure about https.

We have some legacy windows application web service clients that will not be updating their software version soon, and we cannot update their web references to https://service2.domain.com.

Is there any way to leave these web service clients pointing to https://service1.domain.com, but have their requests forwarded to (and responded to by) https://service2.comain.com?

The old server is running IIS 6.0. The new server is running IIS 7.0. We could probably upgrade it to 7.5 if needed, but I'm not certain.

We could also probably make a seamless transition of the old web service to a new server using public DNS, but we cannot change the DNS name of "service1.domain.com."

Thanks ServerFault!

We are about to deploy a bunch of sites to some new servers. I have the following questions about application pools:

1. It seems advisable to have one application pool per website. Are there any caveats to this approach? Will one application pool hog all the CPU, Memory, Etc...?

2. When should you allow multiple worker processes in an application pool? When should you not?

3. Can private memory limit be used to prevent one application pool from interfering with another? Will setting it too low cause valid requests to recycle the application pool without getting a valid response?

4. What is the difference between private and virtual memory limits?

5. Are there compelling reasons NOT to run one application pool per site?

I'm pretty sure this is really a regex question, so you can skip to REGEX QUESTION if you want to skip the background.

Our primary firewall is a Watchguard X750e running Fireware XTM v11.2. We're using webblocker to block most of the categories, and I'm allowing needed sites as they arise. Some sites are simple to add as exceptions, like Pandora radio. That one is just a pattern matched exception with "padnora.com/" as the pattern. All traffic from anywhere on pandora.com is allowed.

I'm running into trouble on more sophisticated domains that reference content off of their base domains. We'll take GrooveShark as a sample. If you go to http://grooveshark.com/ and view page source, you'll see hrefs referring to gs-cdn.net as well as grooveshar.com. So adding a WebBlocker exception to grooveshark.com/ is not effective, and I have to add a second rule allowing gs-cdn.net/ as well.

I see that the WebBlocker allows regex rules, so what I'd like to do in situations like this is create a single regex rule that allows traffic to all the needed domains.

REGEX QUESTION: I'd like to try a regex that matches grooveshark.com/ and gs-cdn.net/. If anybody can help me write that regex, I'd appreciate it.

Here is what is in the WatchGuard documentation from that section: Regular expression

Regular expression matches use a Perl-compatible regular expression to make a match. For example, .[onc][eor][gtm] matches .org, .net, .com, or any other three-letter combination of one letter from each bracket, in order. Be sure to drop the leading “http://” Supports wild cards used in shell script. For example, the expression “(www)?.watchguard.[com|org|net]” will match URL paths including www.watchguard.com, www.watchguard.net, and www.watchguard.org.

Thanks all!

Example:

1. I have a server named server1.domain.local
2. I have lots of CNAME entries in various forward lookup zones pointed to server1.domain.local
3. I want to decomission server1, and have a new server, server2, that is going to replace it.

I need to change all of my CNAMEs that point to server1.domain.local to point to server2.domain.local.

I know I can create server1.domain.local as another CNAME, but I would prefer to just find all the entries and change them individually.

How can I go about finding all references in all forward lookup zones to server.domain.local?

I am migrating a Linux/Apache/PHP website to a server running Windows Server 2008 R2/IIS 7.0.

I have everything working except one minor issue. The file system on the Linux box is case-sensitive and many of the files will have duplicate filenames on Windows.

How would I go about making the folder C:\Website\Site1 case-sensitive so that I can store all the files on the original server there?

If I have to turn on case-sensitivity for the entire server, so be it. There is nothing else running on it.