Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

Re^2: How to debug failure in HTTP::Daemon::SSL->new()

by eye (Chaplain)
on Apr 26, 2014 at 15:51 UTC ( #1083940=note: print w/ replies, xml ) Need Help??


in reply to Re: How to debug failure in HTTP::Daemon::SSL->new()
in thread How to debug failure in HTTP::Daemon::SSL->new()

Since we live in a completely deterministic universe, something has surely changed.

The OP doesn't mention whether the remote server was validated. Maybe it is no longer at 10.0.0.1. Maybe the server has been updated due to some enormous flaw in a widely used library. Maybe the server has a new certificate and there are trust issues. When looking for what has changed, remember that it may not be something you did.

NB: I find it handy to leave comments in my code on how to test external resources (usually needed during development anyway). I prefer commands I can use from a shell prompt as they tend to be more stable over time (IMO).


Comment on Re^2: How to debug failure in HTTP::Daemon::SSL->new()
Re: How to debug failure in HTTP::Daemon::SSL->new()
by jonadab (Parson) on Apr 28, 2014 at 18:33 UTC
    The OP doesn't mention whether the remote server was validated. Maybe it is no longer at 10.0.0.1.

    This is the server code. (The client just uses wget.) And yes, 10.0.0.1 is correct.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1083940]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others examining the Monastery: (9)
As of 2014-10-01 17:56 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    What is your favourite meta-syntactic variable name?














    Results (31 votes), past polls