It might be easiest to have:
--- default.asp
<%
' Some ASP I've forgotten that redirects to
http://example.com:8080/index.htm
%>
And your real site, on port 8080, served up by Apache, will be fine, so long
as the links are absolute, and httpd.conf is configured correctl
AIL PROTECTED]>
-Original Message-
From: Matt Parlane [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 09, 2002 4:41 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [PHP] Dual Server...
Hi Brian...
I have it set up just like Robert, and I really think it's the way to go -
ha
rame and point contents of frame to
apache this should work?
> -Original Message-
> From: Collins, Robert [mailto:[EMAIL PROTECTED]]
> Sent: 09 July 2002 4:41 PM
> To: Brian McGarvie; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: RE: [PHP] Dual Server...
>
>
> I have
t; To: Brian McGarvie; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: RE: [PHP] Dual Server...
>
>
> I have Apache and IIS coexisting on my intranet server and
> the way I set
> them up was to put each on a different port. (Apache serves
> http://intranet
> and IIS serve
Authority
Phone : (504) 248-3826
Fax: (504) 248-3866
Email : [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
-Original Message-
From: Brian McGarvie [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 09, 2002 10:39 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [PHP] Dual Server..
OK following from my thread 'Browser Issues' I have found that when serving the site
from apache, that the aforementioned errors go away... mostly...
OK so... What is the best way to setup so that IIS/Apache co-exist...
I'd like to keep the 'entry' to the site on IIS as we have other sites too.
6 matches
Mail list logo