mirror of
https://github.com/snail007/goproxy.git
synced 2026-04-27 00:15:51 +03:00
[GH-ISSUE #374] --forever and --intelligent parameter work failure #284
Labels
No labels
TODO
bug
duplicate
enhancement
good first issue
help wanted
helpful
invalid
need-confirm
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/goproxy#284
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @wimmerX on GitHub (Jun 2, 2020).
Original GitHub issue: https://github.com/snail007/goproxy/issues/374
--forever and --intelligent parameter work failure
Expected Behavior
1.The forever parameter should make the goproxy program automatically run after the system reboot.
2.The intelligent parameter should be able to automatically implement intelligent-agents according to block and direct,failed to implement the function described in the manual.
Current Behavior
1.After the system restarts, the program does not run automatically.
2.When I use --intelligent=direct all requests did not go to the superior agent,example visiting www.google.com. When I use --intelligent=intelligent,all requests go to the superior agent,example visiting ip138.com.
Context (Environment)
proxy version is : v9.5
full command is :
sudo proxy socks -t tls -p ":18080" -T tls -P "x.x.x.x:18080" -C proxy.crt -K proxy.key --dns-address "8.8.8.8:53" --dns-ttl 300 --intelligent direct --forever --daemon --log proxy.logsystem is :centos 7.3
partial key logs:
2020/06/01 18:33:17 conn [::1]:54948 - play.google.com:443 released
2020/06/01 18:33:59 ip ::1 rate, current: 1/s, max: 20/s
2020/06/01 18:33:59 conn [::1]:55432 - www.youtube.com:443 connected
2020/06/01 18:33:59 conn [::1]:39792 - mtalk.google.com:443 released
2020/06/01 18:33:59 conn [::1]:54700 - www.google.com:443 released
2020/06/01 18:34:02 conn 127.0.0.1:45228 - push.services.mozilla.com:443 released
2020/06/01 18:34:19 clean process 7097
##################manual restart#################
2020/06/02 09:09:12 forever proxy [PID] 13863 running...
2020/06/02 09:09:12 worker proxy [PID] 13935 running...
@snail007 commented on GitHub (Jun 2, 2020):
you are not understand the intelligent mode incorrectly.
@wimmerX commented on GitHub (Jun 2, 2020):
Using
--intelligent=directargument,to access this URL0rz.twwhich belong to the blocked file ,GP should request the parent proxy, while access the URL excluded in the blocked or included in the direct file,It should access directly by the local proxy.isn't it like this?@snail007 commented on GitHub (Jun 2, 2020):
correct
@wimmerX commented on GitHub (Jun 2, 2020):
I found the reason. I originally thought that as long as the parameters
--intelligent=directwere specified, the GP would use the own file in its install directory by default, but I was wrong. Manual andexplicit specified parameters with
-busing path of blocked file still needed.Thanks for your reply.
GP is powerful!
@wimmerX commented on GitHub (Jun 4, 2020):
Will the
--foreverconfiguration parameters restart as the system restarts?The problem mentioned above still exists.
@snail007 commented on GitHub (Jun 4, 2020):
--forever is just a monitor of goproxy's subprocess, no more functions. you understand wrong about it .
@wimmerX commented on GitHub (Jun 4, 2020):
Aha,I get it.