I'm using tomcat 5.5.9 version and when I use the admin app to make any changes to the server.xml file (or evn if I just save, without making any changes), the HTTPS connector definition (if there is one defined) in server.xml gets corrupted. Basically the the attribute "sslProtocol=TLS"" is omitted when saving it. As a result, https connection doesn't work. If I add that attribute manually after I save the changes through the admin app, then https connection works. We noticed a similar problem on tomcat 5.0.28 as well, and I posted a question about this on the tomcat mailing lists last month. In tomcat 5.0.28, the issue was slightly different that when you save changes through the admin webapp, the following duplicate attributes to the HTTPS connector were being added. If we remove those entries manually, then the connector seem to come up fine.
For the storeconfig module, this was fixed in 5.5.10: see http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-catalina/modules/storeconfig/src/share/org/apache/catalina/storeconfig/ConnectorStoreAppender.java?rev=1.3&view=log. Can you please test 5.5.10 and let us know?
Well, when you get a chance to test, please let us know.
Yes, I'd like to test it out. But where I can get 5.5.10 from ? I see 5.5.9 and 5.5.11-alpha from the download page. Would you like me to try 5.5.11-alpha ? thanks (and sorry for the delay in responding to this)
I verified that this works in 5.5.11-alpha. Any idea whether/when the fix will be ported to 5.0.x (currently 5.0.30) ? If the fix is to the admin webapp only, then, can I just take the admin webapp from 5.5.11 and then try it under 5.0.x ? thanks.
This is a bug(perhaps) for EXE installed verion of tomcat5.5.12,the ZIP version is correct. with EXE installed version,if i you edit config file(server.xml) in admin app the http 8080 connector changes to: <connector type="HTTPS" sheme="http"... >
Closing this as fixed since the OP tested it and reported that the issue was fixed in 5.5.11. It is very unlikely that this will be ported to 5.0.x since development has all but stopped on that branch. Comment 5 is not directly related to the original issue. The .exe code and .zip code are identical so the described behaviour is very unexpected. If this is still an issue, please open a new bug report.