On 08/20/2010 02:05 PM, michael bienstein wrote:
Thanks Rainer,
I checked and clearly there is something listening on port 81 but I can't
figure out what it is. When I switxh to port 82 it works as I'd expect.
Use tcpview (
http://technet.microsoft.com/nl-nl/sysinternals/bb897437%28en-us%29.a
_
De : Rainer Jung
À : users@httpd.apache.org
Envoyé le : Ven 20 août 2010, 12h 21min 49s
Objet : [us...@httpd] Re : [us...@httpd] proxy_loadbalancer and failover
On 20.08.2010 12:05, michael bienstein wrote:
Here's the error.log snippet for sending my Chrome browser to
http://localhost:8081/qlikview
The first request gets sent to 127.0.0.1:80 and works. It is a redirect
to /qlikview/index.htm.
The second request gets sent to 127.0.0.1:81. This says that
er Jung
À : users@httpd.apache.org
Envoyé le : Jeu 19 août 2010, 17h 58min 40s
Objet : Re: [us...@httpd] Re : [us...@httpd] proxy_loadbalancer and failover
On 19.08.2010 16:44, michael bienstein wrote:
> Hi,
>
> Thanks for the help. I have a IIS listening on port 80 and nothing on
&g
On 19.08.2010 16:44, michael bienstein wrote:
Hi,
Thanks for the help. I have a IIS listening on port 80 and nothing on
port 81.
Version is Apache/2.2.16 (Win32)
Server Built: Jul 30 2010 16:15:37
Here's the changes I've made to the httpd.config from the default install:
httpd.config
Listen 8
Hi,
Thanks for the help. I have a IIS listening on port 80 and nothing on port 81.
Version is Apache/2.2.16 (Win32)
Server Built: Jul 30 2010 16:15:37
Here's the changes I've made to the httpd.config from the default install:
httpd.config
Listen 8081
#Used in other tests (sticky session cookie
Thanks for the quick reply.
I don't think so. As I said, I did see in the code I have that we can match the
status code against a list of error codes and place the worker into error state
if it matches. This PR looks to be exactly that. I tried it but the stable
release I downloaded refused to
