Problem-
Currently, the API only supports HTTP proxies via plaintext URL parameters (http://user:pass@host:port). This limits protocol flexibility and requires sensitive credentials to be passed in every request string.
Proposed Solution-
SOCKS5 Support: Extend proxy compatibility to include the SOCKS5 protocol for improved performance and security. Proxy Profiles: Implement a "Proxy Settings" section in the dashboard where users can pre-configure and save proxy credentials. Identifier Parameter: Introduce a useproxyid parameter to reference these saved profiles. Example Implementation
Settings: Save host:port:user:pass as ID a1b2c3. API Call: ?useproxyid=a1b2c3 Benefits
Security: Eliminates the need to pass credentials in the URL. Efficiency: Simplifies request strings and reduces overhead. Versatility: Allows users to leverage SOCKS5-specific features.
Please authenticate to join the conversation.
In Progress
Feature Request
13 days ago

Ryan Cobden
Get notified by email when there are changes.
In Progress
Feature Request
13 days ago

Ryan Cobden
Get notified by email when there are changes.