I added configuration.add("tapestry.secure-enabled", "false");
to AppModule.contributeApplicationDefaults. Unfortunately, it didn't seem to make any difference. In production when the login form submits, the url changes from https://secure.mysite.com to http://10.180.54.90:8080 which is the tomcat that the tapestry application resides on. I keep coming back to the BaseURLSource contribution. I don't know why this stuff is happening, but if I understand the use of BaseURLSource--and I very well may not--it seems that it should solve my problem. However, I never see it get called. I am using Tapestry 5.2.5, btw. BaseURLSource isn't specific to 5.3, is it? If I add the following into AppModule.java, what exactly should happen? I'm thinking that any absolute URLs--why there are any absolute URLs in the first place, I don't understand--should come back starting with https://google.com/. Am I misunderstanding the point of this override? @Contribute(ServiceOverride.class) @Log public static void contributeServiceOverrides(MappedConfiguration<Class,Object> configuration) { System.out.println("In here now"); BaseURLSource source = new BaseURLSource() { public String getBaseURL(boolean secure) { System.out.println("returning new URL "); return "https://google.com"; } }; configuration.add(BaseURLSource.class, source); } --Michael On Sep 19, 2011, at 10:49 AM, Lenny Primak wrote: > If your load balancer handles all of your SSL, you should not worry at all > about secureEnabled (disable it) > and it should all work like a champ. > > On Sep 19, 2011, at 11:08 AM, Michael Molloy wrote: >