Hi Johan,
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?
In theory, this link is OK. But the port is exactly the problem in this
case. As far as I figured out there is no option to tell Tapestry which
port to use (without providing a LinkRenderer). It would be OK if there
is no port - but in practice this model simply doesn't work (for me).
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.
The same is true for this one. Just remove the port and it would work ...
I don't know, where exactly the port number is coming from - maybe I
should try Tomcat listening on port 80 directly to omit it ?
Gerald
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
