Re: Unknown system state during get request

["Eric Wasek" <ericw@xxxxxxxxxxxxx>]

Hello Scott,

Thanks for the clarification.  The instructions are also very helpful.

I hope we can collect some useful information.  I think we tried the get 
request, early in our testing, from the address bar of our PC.  I believe it 
was successful.  It may have also been tried with success from a PC at the 
remote location.  Those tries were different than what you are suggesting 
even though they do have their similarities.  The best thing we can do is 
try it and see what it shows.

The new checking that you suggest will probably be performed on Thursday, 
surely no later than Friday.  We will keep you informed of the results of 
this and other checks and tests when they occur.

Eric

----- Original Message ----- 
From: "Scott Klement" <sk@xxxxxxxxxxxxxxxx>
To: "HTTPAPI and FTPAPI Projects" <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Tuesday, November 30, 2010 5:17 PM
Subject: Re: Unknown system state during get request


> hi Eric,
>
>> Regarding openssl - After reading your post and searching the 
>> SystemiNetwork
>> archives for openssl, I read an article that hinted that 5.3 is needed to
>> install openssl and other related software.  Is this true or can it be
>> installed on our 5.1 system?
>
> Sorry, I should've explained better.
>
> My suggestion is to run openssl on your PC.  Connect to both
> Klements.com and the site that fails and look at the difference between
> the certificates they use.  This was just to try to give you more data
> about the problem.  (I'm not even exactly sure what to do with the
> output...  I just figured it'd be a way to try to find differences.)
>
> If you don't have the openssl tool for your PC, you can grab precompiled
> copy of the .EXE file here:
> http://www.scottklement.com/tools/openssl.exe
>
> Save it to your PC hard-drive.  It's a command-line utility, so you'll
> have to open up a Windows "Command Prompt" (MS-DOS prompt) to run it.
> At the prompt, type something like:
>
> openssl s_client -showcerts -connect www.klements.com:443
>
> And it'll connect to port 443 on www.klements.com, and do the SSL
> handshake, et al.  you will then be able to see the certificates that
> get sent back/forth, and lots of information about them.  Then try the
> same thing against the site that doesn't work, and compare the
> differences...
>
> You're right that v5r3 is required to run it on IBM i, but no such
> limitation exists for running it on Windows.
> -----------------------------------------------------------------------
> This is the FTPAPI mailing list.  To unsubscribe, please go to:
> http://www.scottklement.com/mailman/listinfo/ftpapi
> -----------------------------------------------------------------------
>
> 



-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------