You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ See [https://shanetully.com/2014/09/a-dead-simple-webrtc-example/](https://shane
9
9
10
10
Note: This repo is kept updated. The general ideas are there, but the above blog post may be somewhat out of date with the code in this repo.
11
11
12
-
###Usage
12
+
## Usage
13
13
14
14
The signaling server uses Node.js and `ws` and can be started as such:
15
15
@@ -20,15 +20,15 @@ $ node server/server.js
20
20
21
21
With the server running, open a recent version of Firefox or Chrome and visit `https://localhost:8443`. Note the HTTPS! There is no redirect from HTTP to HTTPS!
22
22
23
-
###TLS
23
+
## TLS
24
24
25
25
Recent versions of Chrome require secure websockets for WebRTC. Thus, this example utilizes HTTPS. Included is a self-signed certificate that must be accepted in the browser for the example to work.
26
26
27
-
###Problems?
27
+
## Problems?
28
28
29
29
WebRTC is a rapidly evolving beast. Being an example that I don't check often, I rely on users for reports if something breaks. Issues and pull requests are greatly appreciated.
0 commit comments