Thanks Marc. That might be difficult to do due to some technical
limitations. I will try it out as soon as I get a working
workstation.
John
==
On Wednesday 02/08/2023 at 3:03 am, Marc wrote:
I'm trying to test a new server located at internal IP 192.168.1.5.
The
production ser
>
> I'm trying to test a new server located at internal IP 192.168.1.5. The
> production server lives at IP 192.168.1.7 on the same network.
>
> How can I force the browser to connect to the correct server? If I try
> "http://192.168.1.5"; the redirect on the first (alphabetically) virtual
> se
Hi
do it from my own script directly with httpd (because THAT accepts the -f).
can you give me detail about how you did it?
cordialy,
Le 05/12/2016 à 16:12, Bremser, Kurt (AMOS Austria GmbH) a écrit :
Then I'd look in apachectl what the fullstatus does and do it from my own
script direct
Then I'd look in apachectl what the fullstatus does and do it from my own
script directly with httpd (because THAT accepts the -f).
Kurt Bremser
AMOS Austria
Newton was wrong. There is no gravity. The Earth sucks.
Von: Bertrand Lods [bertrand.l...@ac-caen
Still the wrong list :)
On Thu, Apr 16, 2015 at 1:20 PM, Kevin A. McGrail wrote:
> Sorry, it is not our job to provide support for GetResponse.com Their
> answer is wrong and as best I can tell they have old rules and need to look
> at running sa-update. Telling you to "consult" with us is co
Sorry, it is not our job to provide support for GetResponse.com Their
answer is wrong and as best I can tell they have old rules and need to
look at running sa-update. Telling you to "consult" with us is
completely wrong. Research the product, read our website, sure. They
are clear about tha
Done.
John
===
On Monday 31 December 2012 11:09:58 Ben Johnson wrote:
> On 12/31/2012 10:56 AM, John Iliffe wrote:
> > I would be pleased to do that Nick but I have no experience with
> > bugzilla.
> >
> > If you can give me a short hint in how to go about it I
On Fri, 28 Dec 2012 11:59:41 -0500
John Iliffe wrote:
> That worked, thanks Eric.
>
> It was a positioning problem, mod_fcgid was ahead of mod_unixd in the
> LoadModules list. I just moved it to the end of the list.
>
> I don't like to criticise, but could the documentation for 2.4 be updated
That worked, thanks Eric.
It was a positioning problem, mod_fcgid was ahead of mod_unixd in the
LoadModules list. I just moved it to the end of the list.
I don't like to criticise, but could the documentation for 2.4 be updated
to emphasize this requirement?
http://httpd.apache.org/mod_fcgi
