Commit 521fe271 authored by indexzero's avatar indexzero

[minor] Update README.md to conform to Github flavored markdown

parent c04eec1c
...@@ -224,6 +224,7 @@ You have all the full flexibility of node-http-proxy offers in HTTPS as well as ...@@ -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. 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'),
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment