Please add support to HTTP proxy about translate-shell HOT 3 CLOSED

I guess it would be possible to handle HTTP proxies in gawk, though it was not implemented yet.

For HTTPS: one possible solution is to create a gawk binding of any existing SSL/TLS library (e.g. OpenSSL). Compared to "modern" scripting languages like Python and Ruby (which have almost everything in their standard libraries), that is indeed more difficult.

Using cURL to replace gawk's network layer is a more viable solution and it's on the future plan.

from translate-shell.

I just read your source code. It seems that you manage TCP connections manually.
That will be pretty easy.

Just see these HTTP headers:
Without proxy:

GET /translate_a HTTP/1.1
Host: www.google.com

With proxy:

GET http://www.google.com/translate_a HTTP/1.1
Host: www.google.com

The proxy support can be implemented at Translate.awk:getResponse.
I am not good at awk. So I would be grateful if you can help me do that.

BTW, how do you use translate-shell in China?

from translate-shell.

@m13253 That's not correct. The actual request is GET http://www.google.com/translate_a/..., not GET /translate_a. If you pay attention to the HttpProtocol HttpHost part:

url = HttpProtocol HttpHost "/translate_a/t?client=t"       \
        "&ie=UTF-8&oe=UTF-8"                                    \
        "&text=" preprocess(text) "&sl=" sl "&tl=" tl "&hl=" hl

print "GET " url |& HttpService

The problem is that gawk isn't aware of proxy. Not that only HTTP request line matters.

FYI. I don't use it in China since I don't live in China. Is http://www.google.com inaccessible to you?

from translate-shell.