Great!
If you are interested in the details, the reason is because of the proxiedProtocols properties on the admin-listener, all non-secure access is redirected to secure access and because there is a
mismatch somewhere (maybe your digital certificate is not returning the right host name?)
fails.
In general, the redirection from non-secure to secure end should have worked well, since it is safe by definition.
It worked when you explicitly requested a secure connection from asadmin client. Since both client and server agreed, no redirection happened in that case, which would happen otherwise,
since --secure if false by default!
[Message sent by forum member 'km' (kedar.mhaswade_at_sun.com)]
http://forums.java.net/jive/thread.jspa?messageID=362476