about summary refs log tree commit homepage
path: root/FAQ
diff options
context:
space:
mode:
authorEric Wong <normalperson@yhbt.net>2010-08-16 01:02:30 +0000
committerEric Wong <normalperson@yhbt.net>2010-08-16 01:19:26 +0000
commit2f0ac01589cdc9775f7a5668c4ac491712a9f1b1 (patch)
treeab7291471fb5dd36ba40927266d1800f80e35fdc /FAQ
parenta8f16c6837b56f1a344e4686d029a9a068f69491 (diff)
downloadrainbows-2f0ac01589cdc9775f7a5668c4ac491712a9f1b1.tar.gz
Pound appears to work well in my limited testing with
t/sha1.ru and "curl -T-"
Diffstat (limited to 'FAQ')
-rw-r--r--FAQ11
1 files changed, 8 insertions, 3 deletions
diff --git a/FAQ b/FAQ
index 5c4ea2c..7609d55 100644
--- a/FAQ
+++ b/FAQ
@@ -52,9 +52,14 @@ solution even if nginx will always outperform it in raw throughput.
 
 === How do I support SSL?
 
-If you need a streaming "rack.input" to do upload processing within your
-Rack application, then {stunnel}[http://stunnel.org/] is required.
-Otherwise, nginx is a perfectly good reverse proxy.
+If you need streaming "rack.input" to do on-the-fly upload processing
+within your Rack application, then using an SSL proxy such as
+{Pound}[http://www.apsis.ch/pound/] or {Stunnel}[http://stunnel.org/] is
+required.  Pound has built-in X-Forwarded-For support while Stunnel
+requires a extra {patch}[http://haproxy.1wt.eu/download/patches/].
+
+If you don't need streaming "rack.input", then nginx is a great HTTPS
+reverse proxy.
 
 Refer to the {Unicorn FAQ}[http://unicorn.bogomips.org/FAQ.html] on how
 to ensure redirects go to "https://" URLs.