Odd problem with SSL under OSX

[Avleen Vig]

No route to host means the IP it was resolved to isn't routable (duh, you
knew this ;)

I'm wondering if something is trying to resolve "www.apache.org:443", and
the resolvers you're using are returning an IP you can't route to?

On Mon, Aug 27, 2012 at 8:02 PM, Simon Wistow <simon at thegestalt.org> wrote:

> If I try and install LWP::Protocol::https under OSX (10.6.8) I get a
> failure in its test saying
>
> "Can't connect to www.apache.org:443 (No route to host)"
>
> This is not an Apache only problem - I've tried changing the host.
>
> Installing it on Linux (including a VMWare Ubuntu instance on my
> laptop) and FreeBSD works fine.
>
> So what could be up with it on the host OSX? Curl works fine. Nobody
> else seems to have reported the bug. I'm somewhat stumped.
>
> Any ideas?
>
>