Thank you Kalle. I think its best to have this configurable, only optionally enable this behavior.
On Sep 3, 2013, at 12:37 PM, Kalle Korhonen wrote: > Hairy. The best is always to explicitly set the ports yourself as it > applies to your application. Regardless, I'm thinking of re-opening this > since the current seems more wrong than the old way. > > Kalle > > > On Tue, Sep 3, 2013 at 6:20 AM, Massimo Lusetti <mluse...@gmail.com> wrote: > >> On Tue, Sep 3, 2013 at 10:22 AM, Lenny Primak <lpri...@hope.nyc.ny.us >>> wrote: >> >>> In this issue: https://issues.apache.org/jira/browse/TAP5-1973 >>> >>> If you take a look at the last comment from Alejandro Scandroli, >>> it looks like the side effect is still not fixed in 5.4. >>> Right now, this is being worked around in FlowLogix, but I would like to >>> remove >>> this code (i.e. asking for this bug to get fixed) in 5.4 >>> >>> Thank you >>> >>> >> Does the "issue" pops out only if you don't set HOSTPORT and >> HOSTPORT_SECURE ? >> >> -- >> Massimo Lusetti >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
