HTTP Client and SSL

Using Servoy to administrate the content of your website? Discuss all webrelated Servoy topics on this forum!

HTTP Client and SSL

Postby tshepler » Mon Feb 09, 2009 9:25 pm

I am trying to use the HTTP Client plugin to process a request on an internal website that is SSL enabled. In my testing I was using, well a test server, which wasn't SSL enabled and all worked fine. When I tried to move into production, I got an error:

"PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target "

Is there a solution to this problem?
if not....

Does an HTTP Client plugin call on the server work behind the firewall, or is it a client side call? If its server side I think I can get away with using a non SSL webservice to do my work.
tshepler
 
Posts: 23
Joined: Fri Feb 08, 2008 7:14 pm

Re: HTTP Client and SSL

Postby rgansevles » Mon Feb 16, 2009 11:52 am

The http plugin runs in the client, but when you are using the webclient, all client code runs on the server, so probably inside your firewall.
Smart client code runs on the client machine.

The error indicates that the servers certificate is not signed by a trusted party, you can either add the certificate to all clients or get a trusted signed certificate.


Rob
Rob Gansevles
Servoy
User avatar
rgansevles
 
Posts: 1927
Joined: Wed Nov 15, 2006 6:17 pm
Location: Amersfoort, NL

Secure HTTP Server and Secure HTTP Client

Postby jackthomas » Wed Jul 22, 2009 12:12 pm

A secure HTTP connection means that data sent to and received from an HTTP server are encrypted before being sent out over the Internet. HTTP with SSL encryption provides a secure connection to allow such functions as configuring a router from a web browser. Cisco's implementation of the secure HTTP server and secure HTTP client uses an implementation of the SSL version 3.0. Application layer encryption provides an alternative to older methods such as having to set up a tunnel to the HTTP server for remote management. HTTP over SSL is abbreviated as HTTPS; the URL of a secure connection will begin with https:// instead of http://.

The Cisco IOS HTTP secure server's primary role is to listen for HTTPS requests on a designated port (the default HTTPS port is 443) and to pass the request to the HTTP 1.1 web server. The HTTP 1.1 server processes requests and passes responses (served pages) back to the HTTP secure server, which, in turn, responds to the original request.

The Cisco IOS HTTP secure client's primary role is to respond to Cisco IOS application requests for HTTPS User Agent services, perform HTTPS User Agent services on the application's behalf, and pass the response back to the application.



document scanning
jackthomas
 
Posts: 3
Joined: Mon Jul 20, 2009 11:37 am


Return to Web Development

Who is online

Users browsing this forum: No registered users and 6 guests