What does CFINCLUDE have to do with the port? Further, how does CF even
have anything to do with the port? It is the web server that is doing the
listening on port 80, not CF. It seems to me that there is an architectural
problem here.
DC
----- Original Message -----
From: "Douglas Smith" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Friday, April 20, 2001 15:58
Subject: Re: <cfinclude> to port other than 80?
>
> 1) Why can't you use another IP address and another domain on the same
box,
> and set it up another web site?
>
> 2) Why can't you just run the entire CF application in a sub-directory of
> the existing web site?
>
> At 03:27 PM 4/20/01, Richmond, Alan wrote:
>
> >One of the guys here ran into an interesting problem today when some code
> >was moved out of dev to test. On these test and prod servers there is
> >another application that is using port 80, so CFAS was setup to use
another
> >port. This is the first FB app to go up on this server and the
CFINCLUDEs
> >are breaking because when the path is resolved without a port and then
> >defaults to 80 and the file isn't found. Of course, we can't use an
> >absolute path and using CFHTTP seems like it would be slow.
> >
> >Anybody deal with this? Ideas?
> >
> >Thanks,
> >Alan
> >
> >
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
