starred/whoogle-search

Fork 0

mirror of https://github.com/benbusby/whoogle-search.git synced 2026-04-25 20:25:51 +03:00

[GH-ISSUE #362] [FEATURE] shadowsocks support #240

New issue

Closed

opened 2026-02-25 20:35:14 +03:00 by kerem · 8 comments

kerem commented

2026-02-25 20:35:14 +03:00

Owner

Originally created by @specter78 on GitHub (Jun 19, 2021).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/362

Describe the feature you'd like to see added
Shadowsocks proxy support

Additional context
Since many vpns offer shadowsocks support. And to view results from my country.

Originally created by @specter78 on GitHub (Jun 19, 2021). Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/362  **Describe the feature you'd like to see added** Shadowsocks proxy support **Additional context** Since many vpns offer shadowsocks support. And to view results from my country.

kerem

2026-02-25 20:35:14 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-25 20:35:14 +03:00

Author

Owner

@DUOLabs333 commented on GitHub (Jan 11, 2022):

Do you want shadowsocks specifically (specifying the shadowsocks server), or are you OK with SOCKS support (specifying the shadowsocks client)? The latter should already be in there (WHOOGLE_PROXY_LOC should be socks5h, though it probably should be renamed to WHOOGLE_PROXY_TYPE). What do you think @benbusby?

@DUOLabs333 commented on GitHub (Jan 11, 2022): Do you want `shadowsocks` specifically (specifying the `shadowsocks` server), or are you OK with `SOCKS` support (specifying the `shadowsocks` client)? The latter should already be in there (`WHOOGLE_PROXY_LOC` should be `socks5h`, though it probably should be renamed to `WHOOGLE_PROXY_TYPE`). What do you think @benbusby?

kerem commented

2026-02-25 20:35:14 +03:00

Author

Owner

@benbusby commented on GitHub (Jan 11, 2022):

WHOOGLE_PROXY_TYPE already exists for that purpose, WHOOGLE_PROXY_LOC is for specifying the connection details. To add socks5h support, we'd need to update app/request.py to differentiate between that and regular socks5 connection strings though.

@benbusby commented on GitHub (Jan 11, 2022): `WHOOGLE_PROXY_TYPE` already exists for that purpose, `WHOOGLE_PROXY_LOC` is for specifying the connection details. To add `socks5h` support, we'd need to update `app/request.py` to differentiate between that and regular `socks5` connection strings though.

kerem commented

2026-02-25 20:35:14 +03:00

Author

Owner

@DUOLabs333 commented on GitHub (Jan 11, 2022):

Aren't socks5h paths the same as socks5 paths?

@DUOLabs333 commented on GitHub (Jan 11, 2022): Aren't `socks5h` paths the same as `socks5` paths?

kerem commented

2026-02-25 20:35:14 +03:00

Author

Owner

@benbusby commented on GitHub (Jan 11, 2022):

I assumed socks5h needed to be defined in the connection string (i.e. socks5h://... versus socks5://). I haven't actually looked into it too much yet though, so I could be wrong.

@benbusby commented on GitHub (Jan 11, 2022): I assumed `socks5h` needed to be defined in the connection string (i.e. `socks5h://...` versus `socks5://`). I haven't actually looked into it too much yet though, so I could be wrong.

kerem commented

2026-02-25 20:35:14 +03:00

Author

Owner

@DUOLabs333 commented on GitHub (Jan 11, 2022):

Shouldn't the type be the first part of the connection string, so it doesn't have to be in LOC (it could be just address and port)?

@DUOLabs333 commented on GitHub (Jan 11, 2022): Shouldn't the type be the first part of the connection string, so it doesn't have to be in LOC (it could be just address and port)?

kerem commented

2026-02-25 20:35:14 +03:00

Author

Owner

@benbusby commented on GitHub (Jan 11, 2022):

Currently type isn't included in LOC, but the type is hardcoded to socks5 if it isn't a regular http/https proxy type. But yeah we need to just remove the hardcoded socks5:// part of the current connection string and just use whatever type the user specified.

@benbusby commented on GitHub (Jan 11, 2022): Currently type isn't included in `LOC`, but the type is hardcoded to `socks5` if it isn't a regular http/https proxy type. But yeah we need to just remove the hardcoded `socks5://` part of the current connection string and just use whatever type the user specified.

kerem commented

2026-02-25 20:35:14 +03:00

Author

Owner

@DUOLabs333 commented on GitHub (Jan 11, 2022):

What do you mean, it looks right to me.

@DUOLabs333 commented on GitHub (Jan 11, 2022): What do you mean, it looks right to me.

kerem commented

2026-02-25 20:35:14 +03:00

Author

Owner

@benbusby commented on GitHub (Mar 1, 2022):

Forgot to actually close this. This should supported by the existing socks proxy support in Whoogle. The shadowsocks server location just has to be defined using the WHOOGLE_PROXY_LOC and WHOOGLE_PROXY_TYPE environment variables.

@benbusby commented on GitHub (Mar 1, 2022): Forgot to actually close this. This should supported by the existing socks proxy support in Whoogle. The shadowsocks server location just has to be defined using the `WHOOGLE_PROXY_LOC` and `WHOOGLE_PROXY_TYPE` environment variables.