woo icon indicating copy to clipboard operation
woo copied to clipboard

SSL support

Open fukamachi opened this issue 10 years ago • 9 comments

fukamachi avatar Dec 23 '14 04:12 fukamachi

Is there maybe some hacky way to accept HTTPS requests with Woo? Or do I have to use a different server?

pyankoff avatar Mar 17 '16 09:03 pyankoff

Would be great if woo supported SSL!

Until then, one option is to run Apache with SSL and then woo under that.

gibsonf1 avatar Dec 13 '18 14:12 gibsonf1

I just installed hitch (ssl for libev) and it works perfectly with woo: https://github.com/varnish/hitch

Update: The proxy mechanism with hitch to pass the ip address etc over to woo doesn't work, so not a workable solution after all.

Update2: Installed Haproxy http://www.haproxy.org/ with complete success - IP address is forwarded in the header with "x-forwarded-for"

gibsonf1 avatar Dec 14 '18 01:12 gibsonf1

Since SSL termination normally happens via Nginx/Haproxy in front, I feel it would be best to prioritize the HTTP/2 feature over this one.

wayneeseguin avatar Mar 07 '21 21:03 wayneeseguin

What would be necessary implement this?

fosskers avatar Aug 20 '23 12:08 fosskers

I'm considering whether this layer also has to be as fast as other parts of Woo since it's a characteristic of this web server.

If just using one of an existing library, like cl+ssl or cl-tls, then it wouldn't be so tough job.

This can also be said for HTTP/2 feature.

fukamachi avatar Aug 20 '23 12:08 fukamachi

has to be as fast

Do you mean in order to be fast, a C library should be linked to instead of using native CL implementations of TLS?

I'd personally be willing to accept a performance reduction to achieve TLS support... Woo is already orders of magnitude faster than Hunchentoot :laughing:

fosskers avatar Aug 21 '23 02:08 fosskers

明けましておめでとうございます。 Any thoughts about this issue?

fosskers avatar Jan 11 '24 02:01 fosskers