Apache Server configuration support - https://xxx:80/index.jsp problem (jk2, apache2, tomcat4)

Author

https://xxx:80/index.jsp problem (jk2, apache2, tomcat4)

Jo Kar

2006-02-01, 7:53 am

Hi

I did encounter a strange problem:
We host a servlet (http://www.xxx.de/servlet/ChangeLocale?...), which
sets session attribute according to the user's locale. After the
servlet finishes it forwards to "/index2.jsp". Sometimes this works and
the browser is forwarded (or redirected) to
"http://www.xxx.de/index2.jsp". Sometimes this does not work and the
browser is redirected to "https://www.xxx.de:80/index2.jsp" which is
obiously wrong.

Now to the configuration:
We (my company) is hosting a website with http-access (normal homepage,
presentation) and another part with https-access (applications,
webmail, etc.).
Most content is generated by tomcat4 (4.1.31, j2sdk 1.5) with two
services (http:8080/ajp13:8009 and http:8443/ajp13:18009). Both
services has on host each (www.xxx.de).
The delivery is done by apache2 (2.0.54)with a jk2 connector (2.0.4),
where http is mapped to ajp13:8009 and https is mapped to ajp13:18009.

extract from "workers2.properties"
[lb:http]
[lb:https]

[channel.socket:localhost:8009]
info=Ajp13 forwarding over socket
debug=1
tomcatId=localhost:8009

[channel.socket:localhost:18009]
info=Ajp13 forwarding over socket
debug=1
tomcatId=localhost:18009

[ajp13:localhost:8009]
channel=channel.socket:localhost:8009
group=http

[ajp13:localhost:18009]
channel=channel.socket:localhost:18009
group=https

[uri:www.xxx.de/servlet/*]
group=http

[uri:www.xxx.de:443/*.do]
group=https

In httpd.conf there are "<VirtualHost *:80>" or "<VirtualHost *:443>"
with respective "ServerName www.xxx.de:80" or "ServerName
www.xxx.de:80" defined.

Finally my question:
Where do I have to put my eyes on, to solve this problem?

I suspect some sort of load balancing, but I'm not aware of using such.

If you need more information, like logfiles etc., feel free to ask.

Thanks in advance.
Jo Kar

Davide Bianchi

2006-02-01, 7:53 am

On 2006-02-01, Jo Kar <jk_com@gmx.de> wrote:
> "http://www.xxx.de/index2.jsp". Sometimes this does not work and the
> browser is redirected to "https://www.xxx.de:80/index2.jsp" which is

Well, something that works "sometimes" and does not work "sometimes" is
by definition impossible to fix. Try to nail down when this 'sometimes'
happens (type of browser, type of connection, kind of requests...)
otherwise there is no way to fix it. Is obviously not a problem in
the configuration (otherwise you'll have always the same result).

Davide

--
Windows 2000: Designed for the Internet.
The Internet: Designed for UNIX.
-- From a Slashdot.org post

Jo Kar

2006-02-02, 8:06 am

Davide Bianchi schrieb:

> On 2006-02-01, Jo Kar <jk_com@gmx.de> wrote:
>
> Well, something that works "sometimes" and does not work "sometimes" is
> by definition impossible to fix. Try to nail down when this 'sometimes'
> happens (type of browser, type of connection, kind of requests...)

Neither of them...
'Sometimes' really meant 'after a bunch of requests' (usually around 5,
but also 2,3,4 and 6...).

> otherwise there is no way to fix it. Is obviously not a problem in
> the configuration (otherwise you'll have always the same result).

It definitily was a problem in the configuration, although it didn't
always lead to the "same result".

The real problem was the 'scheme' (hard to find but easy to
copy'n'paste):
I defined a AJP-connector in Tomcat by copy and paste another one. This
other one had the scheme 'https'. The crux were, in this connector my
scheme should've been 'http' and not 'https'.
Ok. 'vi server.xml', edit 'scheme' in the AJP-connector to 'http',
restart tomcat, et voila... here we go...

As I said: hard to find but easy to copy'n'paste.

BTW: I found the most valuable tip here, although it's not directly
related:
http://groups.google.de/group/alt.a...ff23b90835a310c

> Davide

Many thanks Davide for your help.
In this case 'try to nail down' was nearly impossible for me.

Cu
Jo Kar