Thanks Guys, it actually ended up being much simpler, I just needed to specify HOSTPORT_SECURE in my config as port 443 and and HOSTPORT as 80. This seems to have resolved my problem.
On Tue, Jul 2, 2013 at 5:42 PM, Kalle Korhonen <kalle.o.korho...@gmail.com>wrote: > Or, just provide values for the HOST* symbols, see > > http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/services/BaseURLSource.html > . > Also, make sure to configure your servlet container properly. Without any > other information, Tapestry uses the values from the request which may not > be what you want. For example, in your case, you have an external https > handling proxy in front of the servlet container. > > Kalle > > > On Tue, Jul 2, 2013 at 1:58 PM, Lenny Primak <lpri...@hope.nyc.ny.us> > wrote: > > > You probably need to override BaseURLSource like it shows at the bottom > of > > this page: > > http://tapestry.apache.org/https.html > > > > On Jul 2, 2013, at 11:21 AM, George Christman <gchrist...@cardaddy.com> > > wrote: > > > > > Hello, I have an app that runs on a secure intranet using the following > > > configuration, > > > > > > configuration.add(MetaDataConstants.SECURE_PAGE, "true"); > > > > > > When the user adds https to the domain, tapestry generates the > following > > > actionlink which works perfectly. > > > > > > /eprs/login.usernotice > > > > > > However, when a user has a domain with either a blank protocol or http > > > protocol, tapestry generates the following actionlink url for me. > > > > > > https://businessapps:80/eprs/login.usernotice > > > > > > Notice the domain has been added with the wrong port but correct > > protocol. > > > This appears to be causing my actionlinks to break. Does anybody know > how > > > to address this issue? > > > > > > > > > -- > > > George Christman > > > www.CarDaddy.com > > > P.O. Box 735 > > > Johnstown, New York > > > -- George Christman www.CarDaddy.com P.O. Box 735 Johnstown, New York
