Masking the Presence of an IP Proxy from the Browser (https://ipfighter.com/)

未關閉
#529 5 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
15/100
Issue 類型
缺陷
描述清晰度
需要釐清
活躍度
停滯
技術堆疊
c, docker

研究方向

The report describes proxy detection while using the vimagick/tinyproxy image and changing Tinyproxy configuration, but it does not identify a Tinyproxy behavior, code path, or test to investigate. Start by determining what response or connection signal ipfighter uses to identify the proxy, then compare that with Tinyproxy's behavior and documentation. Done would mean a reproducible cause and a supported fix or a clear explanation of the limitation.

由索引模型根據 Issue 內容生成。

描述

feature

We are working on Masking the Presence of an IP Proxy from the Browser.
Specifically, we configured the test Tinyproxy and modified some of its parameters such as DisableViaHeader , ViaProxyName , AddHeader and ConnectPortin the proxy configuration.
However, We still receive the proxy attribute as yes.
In testing the outgoing requests, we did not notice anything out of the ordinary in the headers returned.
We have also checked the official documentation for tinyproxy , we did not found any specific parameter/configuration to mask the proxy info.
This is the docker image we are using FROM vimagick/tinyproxy

主要語言
C
星號
6.1k
分支
768
平均合併
15 天 3 小時
30 天內合併 PR
1

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

tinyproxy/tinyproxy 的其他 Issue

查看 tinyproxy/tinyproxy 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。