Gerald Schöffel wrote:
Hi !
My first project at work I tried to use Tapestry for was canceled because of
deadline constraints and some https-issues I could not solve at that time.
Ok, so I went back to Tapestry in my spare time - I think this framework is
absolutely great. I want to use it for projects at work.
And now (getting around the Login-Page :) ) time is come to implement secure
connections again :(
And I still have absolutely no idea, how to do this.
The 'scheme' binding used on links doesn't work for me - so there is no build
in support for https in my point of view. Kent Tong gave me some hints at that
time (building an own LinkRenderer) but I gave up because it got to complicated.
Why does the included scheme binding not work for me ?
Examples:
Tomcat on local machine, port 8080. The link rendered when using https-scheme
looks like:
https://localhost:8080/myApp/my.page :(
I am just curious but what is wrong with this generated link? It is an
absolute URL and it uses the https scheme. The port is probably not the
HTTPS listener port but how should Tapestry know which port to use? Is
this something you can configure?
Using Apache as a proxy running on port 80, forwarding to localhost on port
8080, the link looks like:
https://mydomain:80/myApp/my.page :(
I know nothing about proxying with apache but is this not right? It
rewrites port 8080 to 80 which I would have guessed is what it should do.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
