Thanks for the answers. We will try adding the "X-Forwarded-Proto:
https" header to our requests.
/Kim
2019-06-14 11:34 skrev Chris Poulsen:
Hi,
We use:
// default to non-secure pages (allows us to support both http and
https
based on the request)
configuration.add(
Hi,
We use:
// default to non-secure pages (allows us to support both http and https
based on the request)
configuration.add( SymbolConstants.SECURE_ENABLED, "false" );
And always have an upstream proxy for performing SSL termination. This
relies on the X-Forward-* headers being set and handled
Hi,
I'd suggest to check value of `Request#isSecure()`, it looks like it's
false.
It can happen if your WebSphere is behind a proxy/load balancer which
terminates SSL,
in this case you may need to configure WebSphere to acknowledge the
x-forwarded-proto HTTP header.
On Fri, Jun 14, 2019 at 9:17
We have a Tapestry application which we need to use over HTTPS only. We
are using Weblogic only.
We have these set in the AppModule of the Tapestry application:
public static void contributeApplicationDefaults(
final MappedConfiguration configuration) {
