thanks for answering! For some reason I have a jetty.xml file aswell as an jetty.xml.in which made changing a bit difficult. Jetty didn't even start with some combinations. Right now I've got it working partially by removing the addConnector parts for http and https (including removing the inititializing of the connectors in the end).
Now I have httpd running on 80 and 443, jetty running ajp on 8009. httpd has a config file with /service, /zimbra, /zimbraAdmin and also /dav. WebDav is working correctly (the partially part...) through httpd into zimbra. Opening /zimbra gets me the login fine and I can enter the my user/pw. Then the mess starts as I get this:
There is apparently somehing wrong with a port 80 in the middle.. In the access log (ssl_access_log) I get this:
invoke unable to parse response DOCTYPE HTML PUBLIC IETFDTD HTML 20ENhtmlheadtitle200 OKtitleheadbodyh1OKh1pThe server is temporarily unable to service yourrequest due to maintenance downtime or capacityproblems Please try again laterphraddressApache223 CentOS Server at localhost Port 80addressbodyhtml
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Apache/2.2.3 (CentOS) Server at xxxxxx.xxx Port 443
and nothing more...
"GET /zimbra HTTP/1.1" 302 -
"GET /zimbra/ HTTP/1.1" 503 941
/zimbraAdmin is similar. I get the login and after the user/pw it goes to loading. No big error but nothing happens. In the access log (ssl_access_log):
which looks very good but nothing happens after this.
"GET /zimbraAdmin/ HTTP/1.1" 200 13662
skin=beach HTTP/1.1" 200 27608
"GET /zimbraAdmin/img/logo/favicon.ico HTTP/1.1" 200 894
css?v=080109202056&skin=beach HTTP/1.1" 200 16169
"GET /zimbraAdmin/js/Ajax_all.js.zgz?v=080109202056 HTTP/1.1" 200 132883
"GET /zimbraAdmin/js/XForms_all.js.zgz?v=080109202056 HTTP/1.1" 200 33902
"GET /zimbraAdmin/js/Zimbra_all.js.zgz?v=080109202056 HTTP/1.1" 200 8714
"GET /zimbraAdmin/js/Admin_all.js.zgz?v=080109202056 HTTP/1.1" 200 202200
So partially working, but I guess I must have messed up the ability for jetty to work when removing the http/https-connector. Although when they were in there httpd refused to start.