From 521fe271853632563143fb4b76c032f7afa7831a Mon Sep 17 00:00:00 2001 From: indexzero Date: Wed, 18 May 2011 21:08:25 -0400 Subject: [PATCH] [minor] Update README.md to conform to Github flavored markdown --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 8da6384..78580ed 100644 --- a/README.md +++ b/README.md @@ -224,6 +224,7 @@ You have all the full flexibility of node-http-proxy offers in HTTPS as well as This is probably the most common use-case for proxying in conjunction with HTTPS. You have some front-facing HTTPS server, but all of your internal traffic is HTTP. In this way, you can reduce the number of servers to which your CA and other important security files are deployed and reduce the computational overhead from HTTPS traffic. Using HTTPS in `node-http-proxy` is relatively straight-forward: + ``` js var fs = require('fs'), http = require('http'),