Changes between Version 32 and Version 33 of doc/meek


Ignore:
Timestamp:
Mar 28, 2014, 7:26:30 AM (5 years ago)
Author:
clan
Comment:

Fix a typo. (GET should be POST)

Legend:

Unmodified
Added
Removed
Modified
  • doc/meek

    v32 v33  
    3030Here's what's happening at a byte level. When meek-client receives a SOCKS request from the Tor client, it generates a random session id string. meek-client makes an HTTP POST to !https://meek-reflect.appspot.com/, which is a special web app set up for this transport. The request looks something like this:
    3131{{{
    32 GET / HTTP/1.1
     32POST / HTTP/1.1
    3333Host: meek-reflect.appspot.com
    3434X-Session-Id: x5ej2h96frvLXeqgKNjIyRDRJidU8RMIeRPDzvLVG+E=
     
    4242The web app running at meek-reflect.appspot.com is very simple: it just copies the POST request it receives, and makes an identical request to a meek-server running on a Tor relay. There is a meek-server instance running at !http://meek.bamsoftware.com:7002/. The request from App Engine to meek-server looks like:
    4343{{{
    44 GET / HTTP/1.1
     44POST / HTTP/1.1
    4545Host: meek.bamsoftware.com:7002
    4646X-Session-Id: x5ej2h96frvLXeqgKNjIyRDRJidU8RMIeRPDzvLVG+E=