This issue respects the following points:
Description of the bug
In the latest version of OpenBullet2.Native-win-x64 which is 2.0.x, when using CurlImpersonate library with “Curl Use Browser Headers” option checked on, OB2 omits some of the headers specified in the Custom Headers section. I've only encountered this with the "Referer" header missing in the sent request's headers that I checked with Fiddler Classic. So I'm not sure about other specific headers that might be filtered out like that.
Reproduction steps
- Start the latest version of OpenBullet2.Native-win-x64
- Open any config and make an Http request block
- Choose the CurlImpersonate option for the Http Library
- Leave the “Curl Use Browser Headers” option checked
- Add any Referer header in the Custom Headers section, like "Referer: https://example.com"
- You can check the actual http request using an MITM proxy like Fiddler Classic and putting its proxy in the Proxy section
- Start it and check the sent request's headers in your MITM proxy tool
- You can see the Referer header is missing
What is the current bug behavior?
Missing an important header in the http requests that are sent using CurlImpersonate with “Curl Use Browser Headers” option checked on, e.g., Referer
What is the expected correct behavior?
Using the header, which in my case is Referer, in the actual http request
Version of the client
2.0.x
Type of client
Native client
Environment
- OS: Windows x64
- Virtualization:
- Browser:
OpenBullet2 logs
Client / Browser logs
No response
Relevant screenshots or videos
No response
Relevant LoliCode if needed
Additional information
No response
This issue respects the following points:
Description of the bug
In the latest version of OpenBullet2.Native-win-x64 which is 2.0.x, when using CurlImpersonate library with “Curl Use Browser Headers” option checked on, OB2 omits some of the headers specified in the Custom Headers section. I've only encountered this with the "Referer" header missing in the sent request's headers that I checked with Fiddler Classic. So I'm not sure about other specific headers that might be filtered out like that.
Reproduction steps
What is the current bug behavior?
Missing an important header in the http requests that are sent using CurlImpersonate with “Curl Use Browser Headers” option checked on, e.g., Referer
What is the expected correct behavior?
Using the header, which in my case is Referer, in the actual http request
Version of the client
2.0.x
Type of client
Native client
Environment
OpenBullet2 logs
Client / Browser logs
No response
Relevant screenshots or videos
No response
Relevant LoliCode if needed
Additional information
No response