<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - WKWebView does not fully support custom NSURLProtocol"
href="https://bugs.webkit.org/show_bug.cgi?id=138169#c27">Comment # 27</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - WKWebView does not fully support custom NSURLProtocol"
href="https://bugs.webkit.org/show_bug.cgi?id=138169">bug 138169</a>
from <span class="vcard"><a class="email" href="mailto:garvankeeley@gmail.com" title="Garvan Keeley <garvankeeley@gmail.com>"> <span class="fn">Garvan Keeley</span></a>
</span></b>
<pre>There is a major bug in the <a href="show_bug.cgi?id=138169#c25">comment #25</a> approach, having a registered NSURLProtocol causes post bodies to be stripped.
Returning false always from NSURLProtocol `canInitWithRequest(request: NSURLRequest) -> Bool` results in an empty post body.
The stripped post body in the NSURLRequest sent to NSURLProtocol is not surprising given the justification in <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - -[WKWebView loadRequest:] ignores HTTPBody in POST requests"
href="show_bug.cgi?id=145410">https://bugs.webkit.org/show_bug.cgi?id=145410</a>, that IPC serialization of large post data is a performance hit. What is surprising is that returning 'false' from `canInitWithRequest` does not workaround this.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>