What platform are you on? (I've had and solved thread-related problems on Win32)

I think the best thing to do here would be to:

1. test that you can get a working HTTPS server working first (and tested against your Java client),
2. then to add a handler to it for SOAP::Lite (and anything else you please... eg: Pod::WSDL).

The following modules all allow you to easily construct an HTTPS server:

• HTTP::Daemon::SSL

  use HTTP::Daemon::SSL;
  use HTTP::Status;
  
  # Make sure you have a certs/ directory with "server-cert.pem"
  # and "server-key.pem" in it before running this!
  my $d = HTTP::Daemon::SSL->new || die;
  print "Please contact me at: <URL:", $d->url, ">\n";
  while (my $c = $d->accept) {
    while (my $r = $c->get_request) {
      if ($r->method eq 'GET' and $r->url->path eq "/xyzzy") {
        # remember, this is *not* recommened practice :-)
        $c->send_file_response("/etc/passwd");
      } else {
        $c->send_error(RC_FORBIDDEN)
      }
    }
    $c->close;
    undef($c);
  }
  [download]

• Net::Server, using Net::Server::Proto::SSL as protocol and Net::Server::Fork as your "personality".
  (This approach seems quite flexible)

• Net::Daemon::SSL

  use Net::Daemon::SSL;
  package MyDaemon;
  @MyDaemon::ISA = qw (Net::Daemon::SSL);
  sub Run
  {
    my $this = shift;
    my $buffer;
    $this->{socket}->print ( "vasja was here\n" );
    $this->{socket}->sysread ( $buffer, 100 );
  
    # Attention! getline() method
    # do not work with IO::Socket::SSL
    # version 0.73
    # see perldoc IO::Socket::SSL
    # for more details
  }
  package main;
  my $daemon = new MyDaemon ( {}, \ @ARGV ); 
  # you can use --help command line key
  $daemon || die "error create daemon instance: $!\n";
  $daemon->Bind();
  [download]

Does at least one of those methods give you a working HTTPS server on your platform?

(Please test with just an SSL-capable webbrowser - ie: Firefox - to rule out the client-side as a problem.)

If you're on windows (not cygwin) and you need to service more than one request simultaneously, you'll need to work around the problems caused by the partial lack of thread-safety in Net::SSLeay. It can be done, but I found it involved writing a much more complicated webserver.

-David

PS: are you definately prohibited from using Apache as your HTTPS/CGI server ? I could not use it in my situation, but it's a much easier solution than writing your own.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.