Bug Description
Proxy URLs with multiple configuration parameters (commonly used with residential sticky IP providers) are not being parsed correctly. When clicking "Check" in the web dashboard, the health check fails with the error:
GET failed: error sending request for url
Affected Proxy URL Format
The following proxy URL format fails:
http://soproxy_hasf6werwq-type-residential-country-de-asn-3320-session-codex1:password123@proxy.soproxy.io:6000
This format includes multiple parameters separated by dashes:
type-residential
country-de
asn-3320
session-codex1
Expected Behavior
The proxy URL should be parsed correctly and the health check should succeed, as these URLs work fine with other proxy clients and tools.
Steps to Reproduce
- Add a proxy with URL format:
http://username-type-residential-country-de-asn-3320-session-xxx:password@host:port
- Click "Check" in the Proxy Assignment dashboard
- Error appears: "GET failed: error sending request for url"
Environment
Additional Context
This URL format is standard for many residential proxy providers (like SoProxy, GeoNode, etc.) that offer sticky sessions with ASN targeting. The issue seems to be related to how the URL parser handles multiple dash-separated parameters in the username portion of the URL.
Request
Please fix this parsing issue in the next update so that residential sticky IP URLs with multiple parameters are supported.
Thank you!
Bug Description
Proxy URLs with multiple configuration parameters (commonly used with residential sticky IP providers) are not being parsed correctly. When clicking "Check" in the web dashboard, the health check fails with the error:
Affected Proxy URL Format
The following proxy URL format fails:
This format includes multiple parameters separated by dashes:
type-residentialcountry-deasn-3320session-codex1Expected Behavior
The proxy URL should be parsed correctly and the health check should succeed, as these URLs work fine with other proxy clients and tools.
Steps to Reproduce
http://username-type-residential-country-de-asn-3320-session-xxx:password@host:portEnvironment
Additional Context
This URL format is standard for many residential proxy providers (like SoProxy, GeoNode, etc.) that offer sticky sessions with ASN targeting. The issue seems to be related to how the URL parser handles multiple dash-separated parameters in the username portion of the URL.
Request
Please fix this parsing issue in the next update so that residential sticky IP URLs with multiple parameters are supported.
Thank you!