Permalink
Browse files

add images to readme

  • Loading branch information...
1 parent 3269024 commit ea4d63b04fc89c78321e9221a1ba95811f8706e5 @igrigorik committed Jun 24, 2012
Showing with 3 additions and 1 deletion.
  1. +3 −1 README.md
View
@@ -7,7 +7,7 @@ Google Chrome supports SPDY/HTTPS as a forward proxy type, which allow us to use
Where does SPDY fit in here? When the SSL handshake is done, the browser and the server can agree to establish a SPDY session by using [SSL NPN][npn] ([RFC][npn-rfc]). If both sides support SPDY, then all communication between browser and proxy can be done over SPDY:
-[IMG]
+![SPDY Proxy Diagram](http://www.igvita.com/posts/12/spdyproxy-diagram.png)
* All browser <-> proxy communication is done over SSL
* SPDY Proxy and Chrome communicate via SPDY (v2)
@@ -67,6 +67,8 @@ $> spdyproxy -k keys/mykey.pem -c keys/mycert.pem -p 44300 -v
$> "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --proxy-pac-url=file:///path/to/config.pac --use-npn
```
+![SPDY Proxy](http://www.igvita.com/posts/12/spdyproxy-demo.png)
+
## Securing the proxy
To run a secure (SPDY) proxy your will need a valid SSL certificate on the server, and also make sure that your client will accept this certificate without any errors. If you're generating a self-signed certificate, then you will need to manually import it into your client keychain - otherwise, the browser will terminate the connection. To create a self-signed certificate:

0 comments on commit ea4d63b

Please sign in to comment.