[Webkit-unassigned] [Bug 140205] WKWebView does not provide a way to set cookie accept policy

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Aug 15 04:58:40 PDT 2019


--- Comment #26 from Niklas Merz <niklasmerz at linux.com> ---
> As a workaround (or hack?) when using the cordova-plugin-ionic-webview: Set
> the "Hostname" preference to the domain of your backend. E.g. if your
> backend is hosted at https://mycool.backend.com set the Hostname to
> "mycool.backend.com" - this tricks the Cookie policy to accept the
> Set-Cookie header since you are a first party domain now... (it seems the
> protocol does not matter as long as the domain is the same). Quite creative
> but it works for us.

Thanks for the workaround. Unfortunately this won't work for us. The app can be  connected to different servers. We absolutely need to do CORS-requests from "ionic://localhost".

What does Webkit do differently in iOS 13 than in iOS12? I built a minimal app that works on iOS 12 and does not work on iOS 13.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20190815/9aa37ca6/attachment.html>

More information about the webkit-unassigned mailing list