>From what they posted, I get the impression they might be trying to hit
the httpd in question from another system doing http://127.0.0.0, and that
certainly would work not, at least not as they might think.
Thanks,
Ron DuFresne
On Thu, 20 Sep 2001, Owen Boyle wrote:
> Jeshua Lacock wrote:
>
> > I was wondering if when creating a test certificate, can the FQDN be
> > 127.0.0.1 or must it be a "live, qualified" domain name? In other words
> > can I enter 127.0.0.1 as the FQDN and ServerName and expect it to work?
> > Currently I am getting a "(HTTPS): Busy, Retry" error...
>
> I can't think of any reason why it shouldn't work... As long as you have
> an SSL VH on 127.0.0.1 you should be able to connect to it. Note that
> you can even have a WRONG IP address in the certificate and SSL will
> still work - you only get a warning in the browser that the certificate
> and site addresses don't match.
>
> I suspect your error message is caused by something other than the use
> of 127.0.0.1...
>
> Rgds,
>
> Owen Boyle.
> ______________________________________________________________________
> Apache Interface to OpenSSL (mod_ssl) www.modssl.org
> User Support Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
> .
> ______________________________________________________________________
> Apache Interface to OpenSSL (mod_ssl) www.modssl.org
> User Support Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
>
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
admin & senior consultant: darkstar.sysinfo.com
http://darkstar.sysinfo.com
"Cutting the space budget really restores my faith in humanity. It
eliminates dreams, goals, and ideals and lets us get straight to the
business of hate, debauchery, and self-annihilation."
-- Johnny Hart
testing, only testing, and damn good at it too!
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
