See https://github.com/whatwg/fetch/pull/1109 and https://bugzilla.mozilla.org/show_bug.cgi?id=1674735.
Created attachment 413156 [details]
This patch modifies the imported WPT tests. Please ensure that any changes on the tests (not coming from a WPT import) are exported to WPT. Please see https://trac.webkit.org/wiki/WPTExportProcess
Uploaded https://github.com/web-platform-tests/wpt/pull/26392 for the specific required changes to upstream.
As per WPT discussion, there is hope to move to using onerror instead of throwing in constructor. This seems nicer indeed but has failed to be implemented in browsers so far.
I'll change WebSocket tests accordingly.
Created attachment 413300 [details]
Patch for landing
Committed r269436: <https://trac.webkit.org/changeset/269436>
All reviewed patches have been landed. Closing bug and clearing flags on attachment 413300 [details].
When it comes to safeguarding your network and data, there's no room for compromise. With the ever-evolving landscape of cyber threats, it's important to stay vigilant and consider all available options to secure your network. One such measure to consider is blocking ports 5060 and 5061, which can provide an added layer of protection against malicious attack. In this blog https://thevacuumwizard.co.uk/product-category/model/dysonv15/ post, we'll explore the implications of blocking these ports, and discuss the potential benefits and drawbacks of doing so.