[long8892]

I will pay well for the problem 👍

I have a link: http s: // www [dot] nhacc uatui [dot] com / bai-hat / chieu-mo-me-kim-khanh [dot] E6boMghcvd9e [dot] html

- when I capture packets with browser extension, the result is correct. Pay attention to /interaction/api/v2/hit-counter

- I used proxifier to fake ip, the result is still true

- however, I interfered with the fiddler in the browser to catch the packet and it produced a false result.

- I tried using Burp instead of fiddler and got the same wrong result.
- note that fiddler and burp do not change anything while the browser is running the link.
- I have also tried to code a browser running on winform (c#) to run like a normal browser and without any interference from fiddler or burp suite. But the results are still wrong.
🤩  My conclusion is that only when running in a pure browser will return the correct results, it seems that website developers can identify browser interference or fake browsers.

🎉  I needed to find the cause and how to overcome it, because I was developing a software that automatically ran that http request instead of a pure browser.

[long8892]

Someone please help me, I've been tired of the problem for a week now

[Ikewin32]

Try sending the request with the header "X-Requested-With: XMLHttpRequest"

[long8892]

Try sending the request with the header "X-Requested-With: XMLHttpRequest"

Thanks for your answer, I tried and still failed

[Ikewin32]

If that wasn't it you most likely need the cookies from the session

---

Hit me up on skype: Ikewin32

I deal with issues like this all the time

[long8892]

If that wasn't it you most likely need the cookies from the session

---

Hit me up on skype: Ikewin32

I deal with issues like this all the time

great!! I sent a skype message to you 🤗

[incognito04]

It most likely needs an unused csrf token.

[long8892]

It most likely needs an unused csrf token.

what is it bro? Sorry for my poor knowledge. Please guide me better.