In case anyone else was interested in how I solved this one - I used
lynx. lynx 2.2.8 comes with SSL support and can easily be called from perl
thus:
open(LYNX,"lynx -source http://boldra.com/ |")
while(<LYNX>) { &do_stuff; }
After finding that I could not get SSL LWP on two more machines (debian &
solaris 2.6) I gave up :(
On Wed, 30 Aug 2000, Paul Boldra wrote:
>
> On Wed, 30 Aug 2000, Tarak Parekh wrote:
>
> > Paul,
> >
> > I am not sure, but did you create certificates for the Apache server on
>installation ?
> >
> > tarak
> >
>
> I am not sure either, since I didn't install apache myself. Do you think
> that this really looks like an apache error?
>
> I thought that because:
> 1. the same response (500) has come from 5 other https servers
> 2. apache seems to handle SSL requests from netscape (running
> locally) fine
> that apache was probably OK.
>
> Your question did prompt me to try listing the response headers in a bit
> more detail; I got this:
> "500 (Internal Server Error) Can't connect to
> www1.bud.dev.mch.mobshop.de:443 (Bad file number)"
>
> ( updated version of my script now at
> http://boldra.com/source/hammer.pl.txt )
>
> I also found an example on Randal Schwarz's site which *kindof* shows you
> how to use https (
> http://web.stonehenge.com/merlyn/WebTechniques/col34.html ). It looks
> like my initial assumpion, that using https via LWP is as easy as using
> http, was correct.
>
> So the problem would seem to be in my LWP, SSLeay or OpenSSL. Any
> thoughts on further debugging?
>
>
> Boldra
>
>
