On 04/09/2012 09:54 PM, Richard Frovarp wrote:
I can verify with the 5.3 archetype, but it certainly seems to me that
production mode of false lets the URLs be relative, but when you set
it to true it starts to do extra work and looking to see if pages are
marked as secured. I'm finding it i
On 04/09/2012 07:44 PM, Howard Lewis Ship wrote:
I don't believe this is about production mode; this is more likely an
artifact of how your app is configured behind your firewall, rather
than how it runs on your workstation ... modulo that, by default in
development mode, secure is disabled.
Whe
Hey Bob, how's it been?
On 04/09/2012 07:01 PM, Bob Harner wrote:
http://tapestry.apache.org/https.html provides a pretty good
description of these options, if you haven't seen it yet.
I honestly did not see that page. Thanks for point it out.
But you're right, this needs to be better docume
I don't believe this is about production mode; this is more likely an
artifact of how your app is configured behind your firewall, rather
than how it runs on your workstation ... modulo that, by default in
development mode, secure is disabled.
When Tapestry detects that an incoming request is not
Hi Richard!
By default Tapestry is trying to be helpful and secure for apps in
which only some of the pages should be running with HTTPS. But when
the whole site should be running with HTTPS you'll need to tell
Tapestry this, and the correct way to do that is to set the
tapestry.secure-enabled sym
I have a simple application in Tapestry 5.3.2. With production mode
false, all of the URLs generated in the pages, including forms, are
relative. This means HTTPS works just fine.
With production mode true, all of the URLs are absolute with HTTP, which
breaks things.
I don't mind the full UR
