I need to setup a really lightweight HTTPS server for a Java application. It's a simulator that's being used in our development labs to simulate the HTTPS connections accepted by a piece of equipment in the wild. Because it's purely a lightweight development tool and isn't used in production in any way at all I'm quite happy to bypass certifications and as much negotiation as I can.
I'm planning on using the HttpsServer
class in Java 6 SE but I'm struggling to get it working. As a test client I'm using wget
from the cygwin command line (wget https://[address]:[port]
) but wget
reports that it was "Unable to establish SSL connection".
If I run wget
with the -d
option for debugging it tells me "SSL handshake failed".
I've spent 30 minutes googling this and everything seems to just point back to the fairly useless Java6 documentation that describes the methods but doesn't actually talk about how to get the darn thing talking or provide any example code at all.
Can anyone nudge me in the right direction?
What I eventually used was this:
To generate a keystore:
See also here.
Potentially storepass and keypass might be different, in which case the
ks.load
andkmf.init
must use storepass and keypass, respectively.Just a reminder to others:
com.sun.net.httpserver.HttpsServer
in the solutions above is not part of the Java standard, but is proprietary and bundled only with the Sun/Oracle JVM, so this will not work on any other Java runtime.There are several lightweight HTTP servers out there that you can embed in your application that support HTTPS and run on any JVM.
One of them is JLHTTP - The Java Lightweight HTTP Server which is a tiny one-file server (or ~50K/35K jar) with no dependencies. Setting up the keystore, SSLContext etc. is similar to the above, since it also relies on the standard JSSE implementation, or you can specify the standard system properties to configure SSL. You can see the FAQ or the code and its documentation for details.
Disclaimer: I'm the author of JLHTTP. You can check it out for yourself and determine if it suits your needs. I hope you find it useful :-)
I updated your answer for a https server(not socket based),It might help with CSRF and AJAX Call
To create a self-signed certificate