I found the following post in jira about the same issue, but this did not work in SEAM 2.0.
I added the following to the components.xml
Has this change been added to to the 2.0 version?
It's moved packages to:
The application failed to deploy after using <navigation:pages>.
I did find a solution by modifying the server.xml for the jboss.web connector. Adding scheme="https" to the Connector set the correct scheme for the HttpServletRequest to return the correct scheme.
Unfortunately, this creates the reverse problem of not being able to connect to the server directly.
This problem of being behind an SSL load balancer seems to be more of a servlet container issue.
<Service name="jboss.web"> <!-- A "Connector" represents an endpoint by which requests are received and responses are returned. Documentation at : Java HTTP Connector: /docs/config/http.html (blocking & non-blocking) Java AJP Connector: /docs/config/ajp.html APR (HTTP/AJP) Connector: /docs/apr.html Define a non-SSL HTTP/1.1 Connector on port 8000 --> <Connector port="8000" scheme="https" maxThreads="250" maxHttpHeaderSize="8192" emptySessionPath="true" protocol="HTTP/1.1" enableLookups="false" redirectPort="8009" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" />
You probably forgot the namespace.