Home > Archive > PERL POE > September 2007 > HTTPS server
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Kevin Scaldeferri 2007-08-07, 7:29 pm |
| I need to add SSL to my web server implemented in POE. At the
moment, I'm familiar with 3 HTTP server implementations:
PoCo::Server::TCP + POE::Filter::HTTPD
PoCo::Server::HTTP
PoCo::Server::SimpleHTTP
Of these, the last seems to be the only one that has an option for
SSL support. Before I start switching my whole app over to using
that library, I'm wondering if there's any other option that I've
missed.
Thanks,
-kevin
| |
| Joel Bernstein 2007-08-07, 7:29 pm |
| On Tue, Aug 07, 2007 at 11:10:16AM -0700, Kevin Scaldeferri wrote:
> I need to add SSL to my web server implemented in POE. At the
> moment, I'm familiar with 3 HTTP server implementations:
>
> PoCo::Server::TCP + POE::Filter::HTTPD
> PoCo::Server::HTTP
> PoCo::Server::SimpleHTTP
>
>
> Of these, the last seems to be the only one that has an option for
> SSL support. Before I start switching my whole app over to using
> that library, I'm wondering if there's any other option that I've
> missed.
Well, PoCo::Server::SimpleHTTP uses PoCo::SSLify to do the SSL stuff.
Would it be more work to rewrite your app to use another library, or to
patch your current http server component to SSLify its socket?
http://search.cpan.org/~apocal/POE-...onent/SSLify.pm
/joel
| |
| Kevin Scaldeferri 2007-08-09, 7:28 pm |
|
On Aug 7, 2007, at 5:07 PM, Joel Bernstein wrote:
> On Tue, Aug 07, 2007 at 11:10:16AM -0700, Kevin Scaldeferri wrote:
>
> Well, PoCo::Server::SimpleHTTP uses PoCo::SSLify to do the SSL stuff.
> Would it be more work to rewrite your app to use another library,
> or to
> patch your current http server component to SSLify its socket?
>
> http://search.cpan.org/~apocal/POE-...y-0.08/lib/POE/
> Component/SSLify.pm
I considered that, but it seems difficult to get access to the socket
from PoCo::Server::TCP (which I've been using). You can do it with
the deprecated Acceptor interface, I think; but I didn't see how to
make it work with the Client* interface.
FWIW, PoCo::Server::SimpleHTTP seems to have once been based on top
of PoCo::Server::TCP, but now uses more low-level. I'm not sure what
the history is here; but it's possible that adding SSL support had
something to do with it.
-kevin
| |
| Matt Sickler 2007-08-09, 10:25 pm |
| The Client* Interface doesnt have a method to expose the socket. A
simple patch to the module should allow it though.
On 8/9/07, Kevin Scaldeferri <kevin@scaldeferri.com> wrote:
>
> On Aug 7, 2007, at 5:07 PM, Joel Bernstein wrote:
>
>
>
> I considered that, but it seems difficult to get access to the socket
> from PoCo::Server::TCP (which I've been using). You can do it with
> the deprecated Acceptor interface, I think; but I didn't see how to
> make it work with the Client* interface.
>
> FWIW, PoCo::Server::SimpleHTTP seems to have once been based on top
> of PoCo::Server::TCP, but now uses more low-level. I'm not sure what
> the history is here; but it's possible that adding SSL support had
> something to do with it.
>
>
> -kevin
>
| |
|
|
|
|
|