The requirement for HTTP/1.1 comes from RFC 6455. Using HTTP/1.0 was
causing interoperability problems in https://bugs.torproject.org/30998.

It appears at least Safari has introduced stricter validation around
this.

https://groups.google.com/forum/#!msg/golang-nuts/eD8dh3T9yyA/l5Ail-xfMiAJ

This changes "2015-12-19" to "2015/12/19" and uses UTC instead of local
time.

I'm more used to the "go build" approach now.

Distributors can rename the binaries if they want to.

This reverts commit c4ef06f0.
This reverts commit f75ce003.

https://gitweb.torproject.org/pluggable-transports/goptlib.git/commit/?id=65fc8d72eccd82237562744ddc85760d426561d8

https://trac.torproject.org/projects/tor/ticket/14135
https://gitweb.torproject.org/pluggable-transports/goptlib.git/commit/?id=50b39b746c6ff34bf31977b658848d876ee84fbf

"pluggable-transport/websocket.git has no license"
https://trac.torproject.org/projects/tor/ticket/10770

http://wiki.creativecommons.org/CC0_FAQ#May_I_apply_CC0_to_computer_software.3F_If_so.2C_is_there_a_recommended_implementation.3F

https://gitweb.torproject.org/pluggable-transports/goptlib.git/commitdiff/b0a3458e272e8f54bb94d7ae346a3362ba018862

Use goptlib instead.

This is something the users is supposed to set for themselves and we
shouldn't mess with it. I went back to relative imports as that seems to
be supported by gccgo now.

http://golang.org/doc/code.html really wants you to take all the Go code
you download and put it in $GOPATH, with imports relative to $GOPATH.
Downloading a repo elsewhere and then doing "go build", like we're used
to with other source packages, doesn't work as well.