On 10/14/2003 08:41 AM Bill Barker wrote:
> "Adam Hardy" <ahardy.struts@(protected)
> news:3F8AA774.7070106@(protected)...
>>
>>Basically it always stays in non-SSL protocol.
>>
>>I posted this in bugzilla, being confident that tomcat was not doing
>>what it was supposed to, but apparently it is. I got the following
>>solution via bugzilla, but I don't understand it! How is this telling me
>>I should configure SSL for the manager login?
>>
>
>
> Pretty simple really:
>  <a href="https://my.host.com/manager">Manager</a>
> And, I agree with Remy's comments in BZ. Unless there is a last-minute
> change in the Servlet 2.4 spec, Tomcat is working as expected. Of course
> the place to complain is: servletapi-feedback@(protected)

Hi Bill,

thanks for answering. Pretty simple indeed. I have no complaints over
the interpretation of the servlet spec.

I do feel that it is inefficient that I should have to find out about
this change in this way - i.e. looking at my app not working as I expect
it to (as it did in the past), thinking I've configured it wrong,
checking all my configuration, mailing the user list, entering an issue
into bugzilla etc.

This issue in the servlet spec does not stand out as something new,
there are no notes on this on the tomcat website, there is nothing in
the Release Notes.

I know what you're going to say: this is open-source, we all do what we
can, perhaps I should monitor the tomcat dev list and write a recap
every month for the user list etc. - touchee I guess.


Thanks anyway,
Adam


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)