Add support to HTTP proxy, fix issue #22

Add support to HTTP proxy, fix issue #22
You are misunderstanding my point here - an absolute URI request line such as `GET http://translate.google.com/translate_a/t?client=t HTTP/1.1` is in no way a malformed HTTP request. According to the spec, a proxy must be able to forward this type of request and the server must be able to handle this (otherwise, no one can access Google Translate via a proxy server!). So the point is, *whether we should use absolute URIs, even without a proxy*.

What I'm saying here is that we could have kept this piece of code **simple and consistent** (not that I care about an additional variable slowing down Awk, we are not aggressive C optimizers!)

You are correct for making this a complete HTTP/1.1 request and I appreciate that :+1: . But I'd say *sending an absolute path instead of absolute URI is not any more like a web browser* (Remember, even with a web browser, people could have proxies too, and proxies are certainly forwarding absolute URIs.) Also, without a sane User-Agent, I'm not sure Google will ever like us. We are ***not a web browser*** anyway (and I prefer not to fake one, unless they want to ban us someday! :smiling_imp:)

(just sayin, this is pretty okay now, until we switch to `curl` or something else in the future. I like SSL/TLS too, but I can't do them from bare-metal! :see_no_evil: )