[Practical Combat] Build an HTTP proxy service based on Tinyproxy

Little scum · Posted on 10/16/2022 12:39:04 PM

Requirements: The security policy of the client server has a whitelist, only the IP of the whitelist can be accessed, the IP address of the company server has been added to the whitelist, because it is very troublesome to find customers to add a whitelist every time, but I want to develop and debug from the home network, at this time, you can build an HTTP proxy service on the company server, generally called a forward proxy, and access the client server can be achieved through the proxy.

Review:

【Practical Action】Use Docker to build an IPsec VPN server
https://www.itsvse.com/thread-10274-1-1.html

Build an ocserv vpn proxy on CentOS 7
https://www.itsvse.com/thread-9409-1-1.html

Tinyproxy is a lightweight HTTP/HTTPS proxy daemon for POSIX operating systems. Designed from the start to be both fast and small, it is an ideal solution for use cases such as embedded deployments that require a full-featured HTTP proxy but cannot use the resources of a larger system.

GitHub address:The hyperlink login is visible.

Build Tinyproxy service based on Docker

Hub Repository:The hyperlink login is visible.

On the HTTP proxy server, the command is as follows:

Login is visible.

【Turn】CURL command uses proxies and proxies are introduced
https://www.itsvse.com/thread-10366-1-1.html

First, the test is not tested without HTTP proxy access, as follows:

Login is visible.

Access via HTTP proxy, the command is as follows:

Login is visible.

You can see that when accessing through an HTTP proxy, the response has become the IP address of the HTTP proxy server, not the IP address of the current network.

Check out the docker container logs as shown below:

(End)

[Practical Combat] Build an HTTP proxy service based on Tinyproxy

Related Posts

Sections viewed