summaryrefslogtreecommitdiff
path: root/obfs4proxy/proxy_http.go
AgeCommit message (Collapse)Author
2015-03-23Change the import path for go.net.Yawning Angel
The Go developers decided to move the go.net repository to golang.org/x/net, and also to transition from hg to git. This wasn't changed when the go.crypto imports were since the 'proxy' component doesn't have imports that break, so the old code still works. While the change here is simple (just update the import location), this affects packagers as it now expects the updated package. Sorry for the inconveneince, I blame the Go people, and myself for not just doing this along with the go.crypto changes.
2014-08-17Massive cleanup/code reorg.Yawning Angel
* Changed obfs4proxy to be more like obfsproxy in terms of design, including being an easy framework for developing new TCP/IP style pluggable transports. * Added support for also acting as an obfs2/obfs3 client or bridge as a transition measure (and because the code itself is trivial). * Massively cleaned up the obfs4 and related code to be easier to read, and more idiomatic Go-like in style. * To ease deployment, obfs4proxy will now autogenerate the node-id, curve25519 keypair, and drbg seed if none are specified, and save them to a JSON file in the pt_state directory (Fixes Tor bug #12605).
2014-05-28Fix minor style issues pointed out by golint.Yawning Angel
2014-05-25Run go fmt on proxy_http.go (No functional changes).Yawning Angel
2014-05-25Add support for HTTP CONNECT proxies.Yawning Angel
Joining a SOCKS dialer on the list of things the Golang runtime really should have is a HTTP CONNECT dialer. There's a full fledged HTTP client and server there, but not this. Why? Who knows. This fixes issue #7.