Skip to content

Commit

Permalink
[minor] Update README.md to conform to Github flavored markdown
Browse files Browse the repository at this point in the history
  • Loading branch information
indexzero committed May 19, 2011
1 parent 521fe27 commit 32a15dd
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Original file line Diff line number Diff line change
Expand Up @@ -224,7 +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. 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: Using HTTPS in `node-http-proxy` is relatively straight-forward:

``` js ``` js
var fs = require('fs'), var fs = require('fs'),
http = require('http'), http = require('http'),
Expand Down

0 comments on commit 32a15dd

Please sign in to comment.