Turns out multiple things were going wrong.
1) The proxy was closing the connection after I read the HTTP CONNECT response. The fix for this had two parts:
++ Adding a "Proxy-Connection: keep-alive" header.
++ Modifying the way I was reading the response. Before, I was reading the inputStream in 256b chunks until Ihit a -1. I changed this to simply read until I hit a line return character since the CONNECT response is onlyone linelong.
After making these changes, I was able to make a socket:// connection to the proxy and then make an ssl:// to the remote server with the proxy connection as the ssl subConnection. However, when I tried to make an ssl:// connection to the server, I was still getting the EOFException when opening the ssl:// connection to the remote server. Then... as if Santa Claus himself dropped in to give me an early Christmas gift... I remembered that I had encountered problems with ssl:// connections before; specifically, writing data to an ssl:// connection's OutputStream REQUIRES a call to OutputStream.flush(). If you don't flush, the data is never written (or the buffer is just really big... in any case, adding a flush() fixes it). Remembering this issue led me to the last part of the fix for this problem.
2) I wrapped the ssl proxy connection and its already opened input and output streams in a class that looks like this:
public class ProxyStreamConnectionWrapper implements StreamConnection {
private StreamConnection stream;
private DataInputStream inputStream;
private DataOutputStream outputStream;
public ProxyStreamConnectionWrapper(StreamConnection stream, DataInputStream dataInputStream, DataOutputStream dataOutputStream) {
this.stream = stream;
this.inputStream = dataInputStream;
this.outputStream = dataOutputStream;
}
public DataInputStream openDataInputStream() throws IOException {
return inputStream;
}
public InputStream openInputStream() throws IOException {
return inputStream;
}
public void close() throws IOException {
stream.close();
}
public DataOutputStream openDataOutputStream() throws IOException {
return new DataOutputStream( openOutputStream() );
}
public OutputStream openOutputStream() throws IOException {
return new OutputStream() {
public void write( byte[] b, int off, int len ) throws IOException {
outputStream.write( b, off, len );
outputStream.flush();
}
public void write( byte[] b ) throws IOException {
outputStream.write( b );
outputStream.flush();
}
public void write( int b ) throws IOException {
outputStream.write( b );
outputStream.flush();
}
};
} I got the idea for this wrapper from a previous post that I've already linked to above. The fix is in the openOutputStream() method. Adding the flush() after every write forces the remote server connection's ssl handshake data out over the proxy server's ssl connection.
merry christmas!
Joe Davis
Developer | Metova
http://www.metova.com
