hmm, ok so I just read this... Links to non-secure pages from a secure page will do the reverse: a complete URL with an "http" protocol will be used. In other words, Tapestry manages the transition from insecure to secure and back again.
So tapestry is writing the http:// that for non-secure pages, but is unaware of the port number. I'd like to secure the whole site at deployment, rather than have SSL running on my test box. Is there a way to do that? It seems I must follow the Tapestry way of @Secure in the pages, but that's not configurable. John ----- Original Message ----- From: John To: users@tapestry.apache.org Sent: Friday, May 31, 2013 8:45 PM Subject: Tapestry links not https My tapestry app doesn't work with SSL set up, the links have port 443 added but start http://. There must be some configuration missing? John
