Hi Chris, me again :)
Yes, those port numbers will go away completely. This is because Apache
won't even be talking to Tomcat on port 8080, it will be using the JK
port, 8009. Using mod_jk makes Tomcat work much more like mod_php or
mod_perl. All of the http/https stuff happens in Apache. So when a
request comes in Apache uses mod_jk to request the (X)HTML (or whatever)
document from Tomcat instead of retrieving a file from the disk. Then
Apache responds with whatever Tomcat sent. From Tomcat's point of view,
there is no http or https.
That sounds really great. But I think I am getting to old for those
things ...
I just downloaded the connector and installed it on my server.
Because things are very new to me, I used a minimal configuration
(without virtual hosts). So I put the following into my httpd.conf:
LoadModule jk_module modules/mod_jk.so
JkWorkerProperty worker.list=ajp13w
JkWorkerProperty worker.ajp13w.type=ajp13
JkWorkerProperty worker.ajp13w.host=localhost
JkWorkerProperty worker.ajp13w.port=8009
JkLogFile c:/jk_log.log
JkLogLevel info
JkMount /myApp/* ajp13w
In server.xml there is the following
<Connector
port="8009"
redirectPort="8443"
protocol="AJP/1.3">
</Connector>
So a very basic setup.
And the connection is running very well - even when I install some
html-files in htdocs in the same directory I have mapped Tomcat to,
Apache will serve the Tomcat stuff. Cool :)
But:
Despite the fact that I am calling my app without the port number (using
http://localhost/myApp) the link rendered by Tapestry when using scheme
https still looks like:
https://localhost:80/myApp/myPage.page :(
Every html-link is rendered ok (http://localhost/myApp/myPage.page)
without the port number.
I have tried every connection (from outside with my domain-name, via
127.0.0.1, from another computer using the servers ip, and the windows
name of the server) - I even configured Apache to listen to port 500 :)
(the https link then was https://localhost:500/Myapp/myPage.page).
I even upgraded to Tapestry 4.0 final (was using Rc1 till now).
So I am clueless again :(
In my configuration (maybe there is some configuration point in Tomcat
or Apache I am not aware of that forces this behaviour ?) this scheme
thing seems to be absolutely useless :(
So I will focus on this filter-thing Fernando mentioned to implement
path or page/component based https-connections.
But I still wonder if I am the only person around trying to use the
scheme https ?
Bye,
Gerald
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
