Delving further into this.
It works fine when adding the @Secure annotation on pages, it is the
global configuration which fails.
On closer investigation, it seems there is a change in where to provide
the global configuration.
When contributing to the application defaults (like below), it works again.
public static void contributeApplicationDefaults(
MappedConfiguration<String, String> configuration )
{
configuration.add( MetaDataConstants.SECURE_PAGE, "true" );
}
Kind regards,
Joachim
Joachim Van der Auwera wrote:
Ok, on further investigation, the "tapestry.secure-enabled=true"
cannot make a difference as this was only added in 5.1.0.1.
When I add the following in my application module
public static void contributeAlias(
Configuration<AliasContribution> configuration )
{
BaseURLSource source = new BaseURLSource()
{
public String getBaseURL( boolean secure )
{
System.out.println( "??????? secure is " + secure );
return "https://localhost:8443";;
}
};
configuration.add( AliasContribution.create(
BaseURLSource.class, source ) );
}
It works again, but this clearly indicates that secure is false,
indicating that the contributeMetaDataLocator is not working.
Has something changed ? Should this now be done differently ?
Thanks for the help,
Joachim
Joachim Van der Auwera wrote:
I am upgrading to from 5.0.18 to 5.1.0.0 and have a problem with
secure pages.
My application is configured to run entirely on https. This was done
by adding the following in my application module:
public static void contributeMetaDataLocator(
MappedConfiguration<String, String> configuration )
{
configuration.add( MetaDataConstants.SECURE_PAGE, "true" );
}
However, all links, forms etc want to redirect to http instead of https.
I have tried both using no configuration and using both
-Dtapestry.production-mode=false -Dtapestry.secure-enabled=true
But it doesn't seem to make a difference.
Any ideas what I am doing wrong?
Thanks,
Joachim
--
Joachim Van der Auwera
PROGS bvba, progs.be
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
