On Wednesday, September 19, 2001, at 03:40 AM, Owen Boyle wrote:
>> Is it possible to have the FQDN 127.0.0.1? Or must it have to be a
>> live
>> domain name?
>>
>> I just am trying to (locally) test the functionality of the software...
>
> The address 127.0.0.1 on all systems is defined as the loopback address.
> So it can be used to establish a socket between transmitting and
> receiving processes on the same machine. The packets will pass through
> the full TCP/IP stack and so the session will emulate a real internet
> session (at least as far as the software is concerned). You don't even
> need a network card.
>
> All you need to do is:
>
> Listen 127.0.0.1:80
> <VirtualHost 127.0.0.1>
> DocumentRoot ...
>
> and then type http://127.0.0.1/ in a browser running on the same
> machine.
Hi,
Thanks for your help Owen. However I apologize for not being more clear
on the issue, please allow me to clarify:
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 am just trying to make sure the SSL layer functions properly...
http://127.0.0.1 works, but not https://127.0.0.1.
I appreciate any help with this matter.
Thanks,
Jeshua Lacock http://OpenOSX.com
Programmer/Owner http://SierraMaps.com
Phone: (760) 935-4736 http://3dTopoMaps.com
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
