6 replies to this topic

[Kway]

I'm playing around and trying to build a FR bot but having an issue when trying to login. What I'm using:

• Windows
• Python 2.7
• Tornado 4.4 (SimpleAsyncHTTPClient)
• unicode_literals
• urllib.urlencode

FR constantly returns incorrect username/password. There is an account lock that I know works however I haven't been able to trigger once during debugging.

 

I have copy and pasted my setup, replaced tornado with mechanize and it works without issue.

 

Hardcoding the body generated from my tornado client fails whereas hardcoding the body generated by mechanize client works perfectly. Both used urllib.urlencode and generate completely identical bodies. Enabling unicode_literals didn't affect mechanize and FR.

 

I am completely lost so if anybody has any ideas, please post.

[Nano]

What I normally do in situations like these is open up Fiddler2 and log the working request and not working request, then compare everything, generated postdata, headers etc.

[Kway]

What I normally do in situations like these is open up Fiddler2 and log the working request and not working request, then compare everything, generated postdata, headers etc.

 

Proxy isn't an option. Wireshark isn't an option either as it is a pain to decrypt the requests. Also tried capturing the requests with a https debug service but all the request data is exactly the same.

[Nano]

Proxy isn't an option. Wireshark isn't an option either as it is a pain to decrypt the requests. Also tried capturing the requests with a https debug service but all the request data is exactly the same.

 

Shouldn't need to set a proxy up for it. I don't when using python.

[Kway]

Shouldn't need to set a proxy up for it. I don't when using python.

Checked and Tornado completely bypasses it.

[Daviid]

Checked and Tornado completely bypasses it.

I use Charles Proxy and set my proxy to 127.0.0.1

[txtsd]

Charles is the way to go