relative vs absolute urls (problem with proxy)

[sztank]

Hi,
I trying to deploy jboss seam application in the following configuration:

Apache as a front server and jboss as as my application server. The users connects to the server through the VPN or SSH tunnels. The apache sever work as a proxy.

(user request) https://foo/bar -> apache proxy -> (jboss) 127.0.0.1:8080/bar

In pages.xml I'm using redirection like this:

<page view-id="/page1.xhtml">
<navigation from-action="#{contractActions.action}">
<redirect view-id="/page2.xhtml"/>



I have the following problems with urls:

Problematic scenario:

1. User started the application using url https://foo/bar/page1

2.User click the action button (h:comandButton)

3. The form is submited

4. User gets a WRONG url in the responce: http://127.0.0.1:8080/bar/page2

So it looks that jboss used absolute url. Is it possible to enforce using the relative url in the above scenario?

In places when the a4j:commandButton is used there is no problem like that. Currently a replace all commandButtons with a4j:buttons and redirect to the proper page in pages.xml but It is awkward.

My jboss administrator is saing that this is jboss/releative/absolute url's configuration issue.

It is my first development using Jboss Seam. I would be very grateful for some advice.

(I using seam 2.0.0.GA)
Best regards!

Stoigniew Sztank

[pmuir]

JSF uses absolute URLs AFAIK. I don't think you can change this. I think you need either to alter the context path of your application to match, or configure some sort of outbound url rewriting.

[sztank]

Thanks for the tip!
Access through the proxy like that it is a common scenario maybe there is some example available of such config or some resources that could helps?

[sztank]

Hi,
I still have this problem:(.. I found this article:

http://javanotepad.blogspot.com/2007/04/problem-sometimes-application-servers.html

but that is about problem with links. I do not have any problem with links, just with form submit.

Please could someone give me some help...
I put much effort and time to know Seam but know I stack with this problem.

[sztank]

Ok, I managed to solve this problem. It was possible to configure Apache reverse proxy to translate jboss http headers (302 redirect). So now the JSF navigation works ok behind the proxy.