l [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 10, 2003 9:22 AM
> To: CF-Talk
> Subject: RE: Restrict IP range for machines that use RDS
>
>
> > Best practice is to do this for live sites anyway.
>
> Well (and this is déjà vu, having just had this conversation
> recently o
> Best practice is to do this for live sites anyway.
Well (and this is déjà vu, having just had this conversation recently on the
CF-Developer list), it *is* damned handy for very minor changes (simple text edits,
global variable value alterations, etc) and when your offline copy is half-way thr
On Monday 10 Mar 2003 14:20 pm, Aidan Whitehall wrote:
> disabling RDS and using A N Other method
Best practice is to do this for live sites anyway.
--
Tom C
"Land of the free, home of the brave... you have to be brave to live there and
enjoy the freedoms"
~~
> We don't use IIS.
> I guess in your set-up (assuming IIS can't do proxying) you could run
your CF
> server (use the JRun it ships with ?), on port X, and install apache
on port
> 80, proxying all request with mod_proxy or something to port X.
OK. Well, for what I'm after, disabling RDS and usi
On Monday 10 Mar 2003 13:17 pm, Aidan Whitehall wrote:
> I'm not sure what you mean by "proxy the CF requests". Do you have IIS
We use the weblogic module, and set it as the handler for the '/' location.
> and Apache on the same machine, with Apache being the default web server
> and handing off
> This is one reason we proxy the CF requests through Apache, we can
just
> use the normal apache allow/deny directives.
I'm not sure what you mean by "proxy the CF requests". Do you have IIS
and Apache on the same machine, with Apache being the default web server
and handing off all requests for
On Monday 10 Mar 2003 10:34 am, Aidan Whitehall wrote:
> With ColdFusion MX is there a way to restrict the IP range of the
> machines that are able to use RDS?
This is one reason we proxy the CF requests through Apache, we can just use
the normal apache allow/deny directives.
--
Tom C
"Land of
7 matches
Mail list logo
