Is webmin in SSL mode properly noticed?

I'm just trying out Nessus 2.2.0rc1 against my Fedora Core 2 workstation
with webmin-1.160 installed in HTTPS mode, and I notice that there are
tonnes of calls from Nessus on port 10000 causing a webmin error.

Webmin acts like IIS in that in HTTPS mode, when you connect:

http://host.name:10000

instead of 

https://host.name:10000

instead of getting a SSL-error (like Apache would do), you get a non-SSL
error page telling you to use the HTTPS frontend.

i.e.

HTTP/1.0 200 Bad Request
Server: MiniServ/0.01
Date: Tue, 26 Oct 2004 00:13:17 GMT
Content-type: text/html
Connection: close

<h1>Error - Bad Request</h1>
<pre>This web server is running in SSL mode. Try the URL <a
href='https://host.name:10000/'>https://host.name:10000/</a> instead.<br></pre>

Maybe Nessus should looks for this and follow it?

I am also going to contact Webmin authors - this looks like a bug to me. An
HTTP 200, followed by "Bad Request"? Is that even RFC-compliant? It should
either be a HTTP error code - or better yet - the redirect code...

-- 
Cheers

Jason Haar
Information Security Manager, Trimble Navigation Ltd.
Phone: +64 3 9635 377 Fax: +64 3 9635 417
PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus