If users need to set both the User-Agent header, and other headers as well, then problems may occur because how that works internally in different browsers. So I've decided to remove setUserAgent and provide a sample how to set it as a custom header (and changed the plugin to handle it properly).
If users need to set both the User-Agent header, and other headers as well, then problems may occur because how that works internally in different browsers. So I've decided to remove
setUserAgentand provide a sample how to set it as a custom header (and changed the plugin to handle it properly).