Dispatcher: HTTPS Masquerade Capability

[clandest]

Make the Dispatcher listen on port 443 for masquerade HTTPS traffic. When it receives masquerade HTTPS traffic, it should unmask it and send it to either the Hopper or the Neighborhood, as appropriate. When it is given Hopper or Neighborhood traffic to send, it should make a decision about how to send the traffic, and if that decision is for HTTPS masquerade traffic, the traffic should be masked as a believable HTTPS request (probably meaning PUT or POST) and sent to port 443.

Make sure the Dispatcher can tell the difference between incoming masquerade HTTPS traffic for the Hopper or the Neighborhood and incoming real HTTPS traffic for the Proxy Server or Proxy Client.

Note from Dan: The last paragraph here has been overtaken by events. If the request arrives on localhost:80, then it's from a browser or other client; if it arrives on 0.0.0.0:*, then it's from outside.