Re: Problems with HTTPS using HTTP API

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

Hi Nick,

Yes, this looks like a bug in my new proxy tunnelling support.  If the 
proxy can't connect the tunnel, HTTPAPI shouldn't attempt an SSL 
handshake -- but obviously, it still does.

I'll look into it.


Nick Townsend wrote:
> Scott,
> 
> Everything has been going well with our testing using HTTPAPI Ver
> 1.21pre1.  So well that we are probably going to be putting the
> application live next week.
> 
> The only minor thing that I have found occurs if I attempt to send a
> request to an invalid https URL. What comes back is a GSKit error
> 'Peer not recognized or badly formatted message received.' rather
> than an http error response code.  See the attached file for the
> debug output for such a request.  If I attempt to send the same
> request using an http URL rather than using https what I get is a 503
> 'Service Unavailable' response from the proxy.
> 
> Is that what you would expect to happen, or is it a bug?  I presume
> that what is happening is that the proxy is sending back a
> non-encrypted response, but the System i is expecting any response to
> be encrypted.
> 
> Regards,
> 
> Nick
> 
> _______________________________ Nick Townsend Technical Leader 
> Endsleigh Insurance Services Limited Telephone: 01242 866866 ext.
> 6426
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------