Skip to content

Commit 521fe27

Browse files
committed
[minor] Update README.md to conform to Github flavored markdown
1 parent c04eec1 commit 521fe27

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

README.md

+1
Original file line numberDiff line numberDiff line change
@@ -224,6 +224,7 @@ You have all the full flexibility of node-http-proxy offers in HTTPS as well as
224224
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.
225225

226226
Using HTTPS in `node-http-proxy` is relatively straight-forward:
227+
227228
``` js
228229
var fs = require('fs'),
229230
http = require('http'),

0 commit comments

Comments
 (0)