What are browser profiles?
Browser profiles define the network profile labels that wreq-js sends to the native layer. Profiles can influence behavior such as:
- TLS handshake preferences
- HTTP protocol behavior
- Default request headers
- Platform-specific header values
Final wire behavior is determined by the native engine and may vary by profile and runtime.
Available browsers
wreq-js profile families include:
- Chrome
- Firefox
- Safari
- Edge
- Opera
- OkHttp
Listing profiles
Using a profile
Specify the browser option in your fetch call:
Operating systems
Different operating systems have different header values and behaviors. Use the os option to emulate a specific platform:
Example: Windows Chrome
Example: iOS Safari
Profile updates
Profile labels are sourced from the native layer and can evolve with upstream updates.
Use a recent version of wreq-js if you want the latest profile set.
By default, browser emulation headers are automatically added. To use only your custom headers: