Hi,
Check your hosts file. It sounds like Netscape is not resolving
https://localhost into an IP address. You have an entry that looks like:
127.0.0.1 localhost
Mike
--
Mike Brandonisio * 3D Modeling and Animation
Tech One Illustration * Print & Interactive Media
mailto: [EMAIL PROTECTED] * Technical Illustration
http://www.techone.org/ * Web & Database Systems
Music For Your Mind
http://www.mp3.com/metzgerscar/
on 9/23/01 6:43 PM, The_polymorph at [EMAIL PROTECTED] scribled:
> Hi.
>
> I seem to be experiencing a similar problem ( sortof ). When I start
> apache and try https://localhost, my browser attempts to connect to a
> search engine on netscape.
>
> Any advice?
>
> Thanks,
>
> -Caitlin.
>
>
>
>
> --- "Michael H. Warfield" <[EMAIL PROTECTED]> wrote:
>> On Sat, Sep 22, 2001 at 06:53:54PM -0600, Mike Brandonisio wrote:
>>> Hi,
>>
>>> I'm getting odd operations on those web sites that have ssl
>> enabled.
>>
>>> I have seemed to have crossed my ports and was wondering if anyone
>> knows how
>>> to correct this. I have a lab server with apache and openssl on it.
>> When I
>>> hit the server with http://192.168.0.60 I get an error saying that
>> the I am
>>> trying to talk to the server in an ssl enabled port try https. I
>> thought
>>> that http was port-80. So I try https and is gives me an error
>> could not
>>> connect to host. I try https://192.168.0.60:80 it makes an ssl
>> connection.
>>> Now here is the odd part I try http://192.168.0.60:443 and it
>> makes
>>> non-secure connection. To summarize it looks like the server is
>> talking ssl
>>> on port80 and plain talk on port443. How do I straighten this out?
>>
>>> When look at the http.conf the only port call outs are in section 2
>> main
>>> server configuration. It has a line:
>>
>>> Port 80
>>
>>> and then in the SSL Support section. It has lines:
>>
>> Ok... I already hear the heard of thundering keyboards about to
>> jump on this...
>>
>>> <IfDefine SSL>
>>> Listen 80
>> ^^^^^^^^^
>> Why did you do this? You just told your web server that if SSL was
>> in effect to listen on that port. SSL should only be on 443, not 80.
>>
>>> Listen 443
>>> </IfDefine>
>>
>>> In addition I have 1 virtual host on 192.168.0.65. It can make
>> connections
>>> on https://192.168.0.65:80 but not http://192.168.0.65:443.
>>
>>> I can seem to figure out how this happened.
>>
>> It did exactly what you told it to. When in SSL mode, it's
>> listening on port 80. Take out that line and try it again.
>>
>>> Mike
>>> --
>>> Mike Brandonisio * 3D Modeling and Animation
>>> Tech One Illustration * Print & Interactive Media
>>> mailto: [EMAIL PROTECTED] * Technical Illustration
>>> http://www.techone.org/ * Web & Database Systems
>>>
>>> Music For Your Mind
>>> http://www.mp3.com/metzgerscar/
>>
>> Mike
>> --
>> Michael H. Warfield | (770) 985-6132 | [EMAIL PROTECTED]
>> (The Mad Wizard) | (678) 463-0932 |
>> http://www.wittsend.com/mhw/
>> NIC whois: MHW9 | An optimist believes we live in the best
>> of all
>> PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of
>> it!
>>
>>
> ______________________________________________________________________
>> OpenSSL Project
>> http://www.openssl.org
>> User Support Mailing List
>> [EMAIL PROTECTED]
>> Automated List Manager
> [EMAIL PROTECTED]
>
>
> =====
>
>
> __________________________________________________
> Do You Yahoo!?
> Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger.
> http://im.yahoo.com
> ______________________________________________________________________
> OpenSSL Project http://www.openssl.org
> User Support Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
