used:
www.clientDomain01.com
www.clientDomain02.com
Seem right?
-Original Message-
From: jqdur...@gmail.com [mailto:jqdur...@gmail.com]
Sent: Thursday, February 24, 2011 9:49 AM
To: cf-talk
Subject: Re: Re: RE: I think I'm confused...
Oops... typo. You will only see
ual domain name. (Without setting up parsing code
to handle the domain variations)
-Original Message-
From: jqdur...@gmail.com [mailto:jqdur...@gmail.com]
Sent: Thursday, February 24, 2011 9:48 AM
To: cf-talk
Subject: Re: RE: I think I'm confused...
Why not use mydomain.com.dev? Then
age-
From: jqdur...@gmail.com [mailto:jqdur...@gmail.com]
Sent: Thursday, February 24, 2011 9:46 AM
To: cf-talk
Subject: Re: Re: RE: I think I'm confused...
I just confirmed that this idea works. The only downside is your NIC will
require static IP addresses.
On Feb 24, 2011 8:38am, jqdur...
I eagerly await your test results!
(and further details!) :o)
-Original Message-
From: jqdur...@gmail.com [mailto:jqdur...@gmail.com]
Sent: Thursday, February 24, 2011 9:39 AM
To: cf-talk
Subject: Re: RE: I think I'm confused...
Jason Fisher's answer is exactly what I
Oops... typo. You will only see ".dev" in DEVELOPMENT. Therefore, you'll
need to strip it off in development, rather than production.
On Feb 24, 2011 8:47am, jqdur...@gmail.com wrote:
> Why not use mydomain.com.dev? Then just strip off the ".dev" before using
> the server name variable while
Why not use mydomain.com.dev? Then just strip off the ".dev" before using
the server name variable while in production. This doesn't really seem like
that big of a hurdle.
On Feb 24, 2011 8:38am, Rick Faircloth wrote:
> Perhaps a good approach might be to use fictitious domains
> locally,
I just confirmed that this idea works. The only downside is your NIC will
require static IP addresses.
On Feb 24, 2011 8:38am, jqdur...@gmail.com wrote:
> Jason Fisher's answer is exactly what I'd do. IIS configuration (assuming
> you're using IIS) is actually the more tedious step. Perhaps a
Jason Fisher's answer is exactly what I'd do. IIS configuration (assuming
you're using IIS) is actually the more tedious step. Perhaps adding an
additional IP to your NIC and pointing your Hosts records at it would
provide simple configuration of IIS for this monster domain app (routing by
8 matches
Mail list logo
