Skip to main content
This article refers to usecases requiring you to both:
  1. Use the same proxy IP along a subsequent flow of requests
  2. Do not allow failover to a different IP in case the first assigned becomes unavailable
This setup can be useful for Residential proxies, which consist of real PCs and mobile devices who may go offline, and you do not wish to switch to another IP in the middle of the workflow to avoid block or detection. To avoid assigning a new peer to the session in case the peer used in the session went offline, use the const parameter, relayed ove the proxy username, in conjunction with the session parameter. Note: for this feature to work both paramaters are necessary. Example, using session: mystring12345 and const together to fix the IP and not allow failover add-session-mystring12345-const to proxy username:
Shell
When using these combined options parameters, if Bright Data cannot assign the previously used proxy IP, you will get a 502 HTTP error code in response, with error message:
Error Message