Bypassing Secure Cookie Limitation in WebKit for Localhost Playwright Testing

Cookie have one of the most crucial attribute, the Secure attribute. This Secure attribute is an option that the server can set when sending cookies to users over HTTP. The purpose of this attribute is to prevent unauthorized access to cookies because they are sent in plain text—thus, browsers that support the Secure attribute will only send/set cookies when requesting a page or resource that uses HTTPS (encrypted). In practice, if you create a web application that can run on all browsers, there will be issues when trying to run it on browsers with the WebKit engine, such as Safari. One bug report mentions inconsistent behavior in WebKit when determining whether localhost is a secure origin. This report is also supported by the consensus status and standardization of the feature to treat localhost or loopback address as secure context in Chrome Platform Status which states that WebKit still does not support it. To address this issue during development, there are several ways to address