Always timing out on OB2 but successful on OB1

Questions
1

OB1

https://*****/p20/user/signIn.html?jtoken=null&device_type=4

**Host: ****
Content-Length: 213
Sec-Ch-Ua: "Chromium";v="91", " Not;A Brand";v="99"
Accept: text/plain, */*; q=0.01
Sec-Ch-Ua-Mobile: ?0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36
Origin: ****
Sec-Fetch-Site: cross-site
Sec-Fetch-Mode: cors
Sec-Fetch-Dest: empty
Referer: ****
Accept-Encoding: gzip, deflate
Accept-Language: en-US,en;q=0.9
**

account_id=&app_ver=null&os_ver=null&web_ver=151&package_id=***&language=en&country=&vip=0&csrf_token=&mail=<USER>&pwd=<PASS>&keep=0&device_type=4&push_token=1&jtoken=null

OB2

Same exact thing except the POST uses <input.USERNAME> and <input.PASSWORD>

I’ve tried all types of proxies on OB2 and still get a timeout on 15 seconds. While OB1 can do it instantly. Any ideas?

2

Remove the Content-Length header from the request, let OB2 generate it automatically, otherwise it will not work.

1 Like
3

Perfect. Thank you very much!