That is right. The expected behaviour from the browsers is to look (from
default) at port 80.
I finally solved the problem by changing *nginx* configuration to listen to
port 81 and apache stayed on port 80.
Everything worked well after that.
Thank you all for your replies!!!
YK
2011/1/10 John D
At 08:59 AM 1/16/2011 +0100, Jørn wrote:
On Saturday 15 January 2011 23:06, Jeroen Geilman wrote:
> On 1/14/11 9:31 AM, Jørn wrote:
> > Hello,
> >
> > This may be a bit off-topic but...
> >
> > During the last months I have noticed this kind of entries in the apache
> > log file:
> >
> > 84.48.
On 1/16/11 12:30 AM, Joost de Heer wrote:
On 01/16/2011 12:19 AM, Jeroen Geilman wrote:
On 1/14/11 5:29 PM, Lukas Sklenar wrote:
Hello,
I have deployed 3 tomcat6.0.29 webapps, each of which exposes a
webservice, and am using apache2.2 and mod_jk-1.2.31-httpd-2.2.3.so to
cluster them - a perfor
On Saturday 15 January 2011 23:06, Jeroen Geilman wrote:
> On 1/14/11 9:31 AM, Jørn wrote:
> > Hello,
> >
> > This may be a bit off-topic but...
> >
> > During the last months I have noticed this kind of entries in the apache
> > log file:
> >
> > 84.48.198.105 - - [09/Jan/2011:12:41:24 +0100]
> >
