State of SSL support

Discussion:

cch1

2016-01-04 23:15:41 UTC

I am trying desperately to get aleph to work with SSL at both ends of a
peer TCP connection. It's clear that the configuration is not symmetric
(aleph.tcp/server accepting a :context parameter and aleph.tcp/client not).

I've gotten over the lack of symmetry by rebinding
aleph.netty/ssl-client-context to always return my full blown custom
context), but even then I'm stymied. Many of my problems may come from a
lack of understanding of netty SSL support in 4.1.0.Beta8 (which
frustratingly seems to be in flux).

Has anybody successfully gotten SSL on TCP at both the client and the
server in Aleph 0.4.1-SNAPSHOT?

Has anybody successfully gotten SSL on TCP at both the client and the
server in netty 4.1.0.Beta8?

-Chris

--
You received this message because you are subscribed to the Google Groups "Aleph" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aleph-lib+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Timothy Washington

2016-02-21 20:48:07 UTC

Permalink

One more question. Under an SSL connection, I'm returning several static
resources (js, css, etc). In this case, a *ring.util.response/file-response*
is successfully returning a response in a ring handler, back to aleph. But
I do notice there's no *:content-type*.

{:status 200,
:headers
{"Content-Length" "511",
"Last-Modified" "Sun, 21 Feb 2016 20:15:23 GMT"},
:body
#object[java.io.File 0x28139022 "resources/public/js/mycode.js"]}

This works perfectly fine when I'm returning my index.html. Does the
*:content-type* or something else need to be set, when returning a file
response?

{*:content-type "text/html",*
:body
"<!DOCTYPE html>\n<html>\n ...</html>\n"}

Thanks
Tim

Hey Zach, thanks for responding.
...

Timothy Washington

2016-02-22 03:34:10 UTC

Permalink

Ok, fixed this problem. Turns out you just need to return the file
contents, not the file object. That should have been obvious, lol.

Just for future reference.

Tim

Post by Timothy Washington
One more question. Under an SSL connection, I'm returning several static
resources (js, css, etc). In this case, a
*ring.util.response/file-response* is successfully returning a response
in a ring handler, back to aleph. But I do notice there's no
*:content-type*.
{:status 200,
:headers
{"Content-Length" "511",
"Last-Modified" "Sun, 21 Feb 2016 20:15:23 GMT"},
:body
#object[java.io.File 0x28139022 "resources/public/js/mycode.js"]}
This works perfectly fine when I'm returning my index.html. Does the
*:content-type* or something else need to be set, when returning a file
response?
{*:content-type "text/html",*
:body
"<!DOCTYPE html>\n<html>\n ...</html>\n"}
Thanks
Tim

Hey Zach, thanks for responding.
...