starred/goproxy

Fork 0

mirror of https://github.com/snail007/goproxy.git synced 2026-04-27 00:15:51 +03:00

[GH-ISSUE #260] source code ? #180

New issue

Closed

opened 2026-02-27 23:15:48 +03:00 by kerem · 8 comments

kerem commented

2026-02-27 23:15:48 +03:00

Owner

Originally created by @boianmihailov on GitHub (Apr 11, 2019).
Original GitHub issue: https://github.com/snail007/goproxy/issues/260

Where is the actual source for v7.3 ?
Repo seems to contain 3.0 and lacks the options available in the binaries.

Great job, btw!

Originally created by @boianmihailov on GitHub (Apr 11, 2019). Original GitHub issue: https://github.com/snail007/goproxy/issues/260 Where is the actual source for v7.3 ? Repo seems to contain 3.0 and lacks the options available in the binaries. Great job, btw!

kerem

2026-02-27 23:15:48 +03:00

closed this issue
added the
wontfix
label

kerem commented

2026-02-27 23:15:49 +03:00

Author

Owner

@UrielCh commented on GitHub (Apr 13, 2019):

your proxy look awsome, but the source code do not match the binary.

@UrielCh commented on GitHub (Apr 13, 2019): your proxy look awsome, but the source code do not match the binary.

kerem commented

2026-02-27 23:15:49 +03:00

Author

Owner

@UrielCh commented on GitHub (Apr 13, 2019):

you can check the source code from:
https://gitlab.com/czoo00/goproxy/
it's still not the right version but it's more up to date.

@UrielCh commented on GitHub (Apr 13, 2019): you can check the source code from: https://gitlab.com/czoo00/goproxy/ it's still not the right version but it's more up to date.

kerem commented

2026-02-27 23:15:49 +03:00

Author

Owner

@UrielCh commented on GitHub (Apr 13, 2019):

from the README:

Source code declaration

The author of this project found that a large number of developers based on the project for secondary development or using a large number of core code of the project without complying with the GPLv3 agreement, which seriously violates the original intention of using the GPLv3 open source agreement in this project. In view of this situation, the project adopts the source. The code delays the release strategy, to a certain extent, to curb these behaviors that do not respect open source and do not respect the labor results of others.
This project will continue to update the iterations, and continue to release the full platform binary program, providing you with powerful and convenient proxy tools.
If you have customized, business needs, please send an email to arraykeys@gmail.com

@UrielCh commented on GitHub (Apr 13, 2019): from the README: ### Source code declaration The author of this project found that a large number of developers based on the project for secondary development or using a large number of core code of the project without complying with the GPLv3 agreement, which seriously violates the original intention of using the GPLv3 open source agreement in this project. In view of this situation, the project adopts the source. The code delays the release strategy, to a certain extent, to curb these behaviors that do not respect open source and do not respect the labor results of others. This project will continue to update the iterations, and continue to release the full platform binary program, providing you with powerful and convenient proxy tools. If you have customized, business needs, please send an email to `arraykeys@gmail.com`

kerem commented

2026-02-27 23:15:49 +03:00

Author

Owner

@boianmihailov commented on GitHub (Apr 14, 2019):

I've read that, yet I am having trust issues.
So if the License says GPLv3, but the author is not releasing sources ... thank god Linus Torvalds is not feeling the same about "secondary development"

@boianmihailov commented on GitHub (Apr 14, 2019): I've read that, yet I am having trust issues. So if the License says GPLv3, but the author is not releasing sources ... thank god Linus Torvalds is not feeling the same about "secondary development"

kerem commented

2026-02-27 23:15:49 +03:00

Author

Owner

@UrielCh commented on GitHub (Apr 14, 2019):

All the sources had been removed 4 month ago, and the news version deny launch inside a secured container.
issue 263.

lastest version of goproxy can't running in docker

May be you should not use this software outside of china mainland...

@UrielCh commented on GitHub (Apr 14, 2019): All the sources had been removed 4 month ago, and the news version deny launch inside a secured container. [issue 263](https://github.com/snail007/goproxy/issues/263). `lastest version of goproxy can't running in docker` May be you should not use this software outside of china mainland...

kerem commented

2026-02-27 23:15:49 +03:00

Author

Owner

@YanzheL commented on GitHub (May 10, 2019):

I've read that, yet I am having trust issues.
So if the License says GPLv3, but the author is not releasing sources ... thank god Linus Torvalds is not feeling the same about "secondary development"

Truly agree. It's a shame that this project is ruined by this dishonest behavior. Really sucks.

@YanzheL commented on GitHub (May 10, 2019): > I've read that, yet I am having trust issues. > So if the License says GPLv3, but the author is not releasing sources ... thank god Linus Torvalds is not feeling the same about "secondary development" Truly agree. It's a shame that this project is ruined by this dishonest behavior. Really sucks.

kerem commented

2026-02-27 23:15:49 +03:00

Author

Owner

@brlin-tw commented on GitHub (Jul 19, 2022):

To be fair regardless of the license of the code declared to be the author/copyright holder has the right to determine whether or not to release the source code of (part) of their software. Intellectual licenses are for restricting third parties' rights instead of the copyright holders'.

Though I still hope that:

The current public code remains to be buildable and at least partially usable, also the corresponding version of the built product is declared.
The old releases on the project site are preserved.

@brlin-tw commented on GitHub (Jul 19, 2022): To be fair regardless of the license of the code declared to be the author/copyright holder has the right to determine whether or not to release the source code of (part) of their software. Intellectual licenses are for restricting third parties' rights instead of the copyright holders'. Though I still hope that: * The current public code remains to be buildable and at least partially usable, also the corresponding version of the built product is declared. * The old releases on the project site are preserved.

kerem commented

2026-02-27 23:15:49 +03:00

Author

Owner

@shaxiaozz commented on GitHub (Nov 12, 2024):

I used go build to compile the output. Enter: goproxy http --help, which lacks many parameter options.

Using goproxy --version, I got 3.0, which seems to indicate that this repository is not a complete code

@shaxiaozz commented on GitHub (Nov 12, 2024): I used go build to compile the output. Enter: ```goproxy http --help```, which lacks many parameter options. Using ```goproxy --version```, I got 3.0, which seems to indicate that this repository is not a complete code

kerem referenced this issue

2026-02-27 23:17:23 +03:00

[PR #180] [CLOSED] Add proxy internal ip config to force internal ip go through parent proxy #547