test site on a live site using SSL

I’ve set up a test site on the client’s live web server. Their live site is
www.bla.com, I’ve created test.bla.com. The test site is a “fake” subdomain,
only accessible by adding the domain/IP in the Hosts file.

The web server is running IIS and ISA v.3.0.1200 with SP2.

Both the live and test sites are done in ASP. (not .NET), and have both a
public and private section. The private section uses SSL.

When I make a change to a “secured” page and put it on the test site, I can
access the page via regular http: (not https:). If I change the URL to use
https:, I no longer see the changes I made to the page on the test site.
Through a bit of checking, I’ve determined that when I add the “s” (and thus
go to https:), I get served up the live site’s copy of the page, which
obviously doesn’t include the changes I made.

In ISA, both domains (live and test) are entered as destinations under web
publishing rules for https. Caching is turned off in all cases.

I also have restarted IIS, ISA and the server itself with no effect.

What am I missing to allow the secure sections of the test site to work
properly under https:?

Re: test site on a live site using SSL

On Oct 10, 10:48 am, charlesET
wrote:
> I've set up a test site on the client's live web server. Their live site iswww.bla.com, I've created test.bla.com. The test site is a "fake" subdomain,
> only accessible by adding the domain/IP in the Hosts file.
>
> The web server is running IIS and ISA v.3.0.1200 with SP2.
>
> Both the live and test sites are done in ASP. (not .NET), and have both a
> public and private section. The private section uses SSL.
>
> When I make a change to a "secured" page and put it on the test site, I can
> access the page via regular http: (not https:). If I change the URL to use
> https:, I no longer see the changes I made to the page on the test site.
> Through a bit of checking, I've determined that when I add the "s" (and thus
> go to https:), I get served up the live site's copy of the page, which
> obviously doesn't include the changes I made.
>
> In ISA, both domains (live and test) are entered as destinations under web
> publishing rules for https. Caching is turned off in all cases.
>
> I also have restarted IIS, ISA and the server itself with no effect.
>
> What am I missing to allow the secure sections of the test site to work
> properly under https:?


This sounds like network misconfiguration because when you use HTTPS
you are going to the live site, not test site. I don't think caching,
IIS, or ISA have anything to do with your issue.

I've seen problems like this when my client machine is running ISA
Client, where regardless of my HOSTS setting, I get routed to the
external site and not via HOSTS settings.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Re: test site on a live site using SSL

Any suggestions on how to overcome this? We have disabled the ISA client and
the browsers proxy settings are disabled just to get to where we are now.

"David Wang" wrote:

> On Oct 10, 10:48 am, charlesET
> wrote:
> > I've set up a test site on the client's live web server. Their live site iswww.bla.com, I've created test.bla.com. The test site is a "fake" subdomain,
> > only accessible by adding the domain/IP in the Hosts file.
> >
> > The web server is running IIS and ISA v.3.0.1200 with SP2.
> >
> > Both the live and test sites are done in ASP. (not .NET), and have both a
> > public and private section. The private section uses SSL.
> >
> > When I make a change to a "secured" page and put it on the test site, I can
> > access the page via regular http: (not https:). If I change the URL to use
> > https:, I no longer see the changes I made to the page on the test site.
> > Through a bit of checking, I've determined that when I add the "s" (and thus
> > go to https:), I get served up the live site's copy of the page, which
> > obviously doesn't include the changes I made.
> >
> > In ISA, both domains (live and test) are entered as destinations under web
> > publishing rules for https. Caching is turned off in all cases.
> >
> > I also have restarted IIS, ISA and the server itself with no effect.
> >
> > What am I missing to allow the secure sections of the test site to work
> > properly under https:?
>
>
> This sounds like network misconfiguration because when you use HTTPS
> you are going to the live site, not test site. I don't think caching,
> IIS, or ISA have anything to do with your issue.
>
> I've seen problems like this when my client machine is running ISA
> Client, where regardless of my HOSTS setting, I get routed to the
> external site and not via HOSTS settings.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>
>

Re: test site on a live site using SSL

I don't have any more suggestions.

I would first verify that the HTTPS traffic is actually going to the
right IIS server (using IIS's logs). If your HTTPS traffic is getting
routed to the live site, this is obviously not an IIS-related issue --
the request isn't even getting to the right server.

If the request is getting to the right IIS server, and you have
restarted IIS, then the issue is not with any IIS caching -- you just
restarted IIS and flushed all its caches.

You then have to check every single cache possible between your client
and server. Restarting IIS gets rid of IIS cache from the picture.

At this point, this question is completely off-topic since it has
nothing to do with IIS and specific to your networking configuration.
I can only say that I don't see your behavior of HTTP/HTTPS not seeing
the same content/changes when they point to the same physical
directory.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//



On Oct 11, 8:23 am, charlesET
wrote:
> Any suggestions on how to overcome this? We have disabled the ISA client and
> the browsers proxy settings are disabled just to get to where we are now.
>
>
>
> "David Wang" wrote:
> > On Oct 10, 10:48 am, charlesET
> > wrote:
> > > I've set up a test site on the client's live web server. Their live site iswww.bla.com, I've created test.bla.com. The test site is a "fake" subdomain,
> > > only accessible by adding the domain/IP in the Hosts file.
>
> > > The web server is running IIS and ISA v.3.0.1200 with SP2.
>
> > > Both the live and test sites are done in ASP. (not .NET), and have both a
> > > public and private section. The private section uses SSL.
>
> > > When I make a change to a "secured" page and put it on the test site, I can
> > > access the page via regular http: (not https:). If I change the URL to use
> > > https:, I no longer see the changes I made to the page on the test site.
> > > Through a bit of checking, I've determined that when I add the "s" (and thus
> > > go to https:), I get served up the live site's copy of the page, which
> > > obviously doesn't include the changes I made.
>
> > > In ISA, both domains (live and test) are entered as destinations under web
> > > publishing rules for https. Caching is turned off in all cases.
>
> > > I also have restarted IIS, ISA and the server itself with no effect.
>
> > > What am I missing to allow the secure sections of the test site to work
> > > properly under https:?
>
> > This sounds like network misconfiguration because when you use HTTPS
> > you are going to the live site, not test site. I don't think caching,
> > IIS, or ISA have anything to do with your issue.
>
> > I've seen problems like this when my client machine is running ISA
> > Client, where regardless of my HOSTS setting, I get routed to the
> > external site and not via HOSTS settings.
>
> > //David
> >http://w3-4u.blogspot.com
> >http://blogs.msdn.com/David.Wang
> > //- Hide quoted text -
>
> - Show quoted text -