tinyproxy | weight HTTP/HTTPS proxy daemon | HTTP library

by tinyproxy C Version: 1.11.1 License: GPL-2.0

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | tinyproxy Summary

tinyproxy is a C library typically used in Networking, HTTP applications. tinyproxy has no bugs, it has a Strong Copyleft License and it has medium support. However tinyproxy has 1 vulnerabilities. You can download it from GitHub.

Tinyproxy is a small, efficient HTTP/SSL proxy daemon released under the GNU General Public License. Tinyproxy is very useful in a small network setting, where a larger proxy would either be too resource intensive, or a security risk. One of the key features of Tinyproxy is the buffering connection concept. In effect, Tinyproxy will buffer a high speed response from a server, and then relay it to a client at the highest speed the client will accept. This feature greatly reduces the problems with sluggishness on the Internet. If you are sharing an Internet connection with a small network, and you only want to allow HTTP requests to be allowed, then Tinyproxy is a great tool for the network administrator. For more info, please visit the Tinyproxy web site.

Support

Quality

Security

License

Reuse

Support

tinyproxy has a medium active ecosystem.

It has 3949 star(s) with 608 fork(s). There are 101 watchers for this library.

It had no major release in the last 12 months.

There are 96 open issues and 267 have been closed. On average issues are closed in 77 days. There are 11 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of tinyproxy is 1.11.1

Quality

tinyproxy has 0 bugs and 0 code smells.

Security

tinyproxy has 1 vulnerability issues reported (0 critical, 1 high, 0 medium, 0 low).

tinyproxy code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

tinyproxy is licensed under the GPL-2.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

tinyproxy releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

It has 431 lines of code, 0 functions and 4 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of tinyproxy

Get all kandi verified functions for this library.

tinyproxy Key Features

No Key Features are available at this moment for tinyproxy.

tinyproxy Examples and Code Snippets

No Code Snippets are available at this moment for tinyproxy.

Community Discussions

Trending Discussions on tinyproxy

tinyproxy: How to manually install the most recent version 1.11.0 on Ubuntu?

How to get data from the client and not from the server or my web application?

Is it possible to setup tinyproxy as a forward-proxy and reverse-proxy at the same time?

QUESTION

tinyproxy: How to manually install the most recent version 1.11.0 on Ubuntu?

Asked 2022-Apr-03 at 12:15

I would like to install the most recent tinyproxy version 1.11.0 on Ubuntu. How can I do that?

Unfortunetly does sudo apt update; sudo apt install tinyproxy -y; not work for me and only gives me the most recent stable version 1.10.0 from 2018.

So I tried to download and unzip the most recent version on GitHub https://github.com/tinyproxy/tinyproxy/releases

But I couldn't get it to work properly installed yet.

What I tried so far:

...

ANSWER

Answered 2022-Apr-03 at 12:15

Make sure you update the system with the latest packages

Source https://stackoverflow.com/questions/71717463

QUESTION

How to get data from the client and not from the server or my web application?

Asked 2021-Jan-11 at 03:22

I am trying to get user data not from my server.

I have two pages on one I have an SSL certificate and on the other I don't, I am printing data from my computer, on the SSL certificate, it prints port 443 while the one without a certificate prints port 80.

...

ANSWER

Answered 2021-Jan-11 at 03:03

Only on the page without certificate, it detects me when I use a VPN app

When the proxy connects to an encrypted webserver(SSL) it CAN'T modify the headers it's user sending to the final server, because all data is encrypted.

However, if the proxy is connecting to a non encrypted webserver, it will add it's own headers like HTTP_FORWARDED_FOR

That is why you detected the proxy on non encrypted webserver, because 1 of these 25 conditions has trapped the proxy!

That is why detecting a proxy on an encrypted webserver is hard, and you have to do more complicated approaches like trying to make port-scan the client IP and check if any of the common/standard proxies ports are open.

You can confirm this by doing a var_dump($_SERVER) in your code , and you will see that on the page with SSL, there are no proxy headers at all, and in the page without SSL I'm sure you will find one of them.

As I told you in your previous question, I suggest using an IP reputation API.

Source https://stackoverflow.com/questions/65660567

QUESTION

Is it possible to setup tinyproxy as a forward-proxy and reverse-proxy at the same time?

Asked 2020-Jul-20 at 21:01

I want to setup tinyproxy as forward-proxy and reverse-proxy at the same time. Is it possible? If yes, what does the config look like? And is there any limit or concern?

...

ANSWER

Answered 2020-Jul-20 at 21:01

Found the following instruction in tinyproxy documentation:

Source https://stackoverflow.com/questions/62958457

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install tinyproxy

Tinyproxy uses a standard GNU configure script based on the automake system. If compiling from a git checkout, you need to first run. from the top level directory to generate the configure script. The release tarball contains the pre-created configure script, so when building from a release, you can skip this step. Then basically all you need to do is.
--enable-debug: If you would like to turn on full debugging support.
--enable-xtinyproxy: Compile in support for the XTinyproxy header, which is sent to any web server in your domain.
--enable-filter: Allows Tinyproxy to filter out certain domains and URLs.
--enable-upstream: Enable support for proxying connections through another proxy server.
--enable-transparent: Allow Tinyproxy to be used as a transparent proxy daemon. Unlike other work modes, transparent proxying doesn't require explicit configuration and works automatically when traffic is redirected to the proxy using the appropriate firewall rules.
--enable-reverse: Enable reverse proxying.
--with-stathost=HOST: Set the default name of the stats host.