<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#c28">Comment # 28</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:pavel@salsitasoft.com" title="Pavel Zdenek <pavel@salsitasoft.com>"> <span class="fn">Pavel Zdenek</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=138169#c27">comment #27</a>)
<span class="quote">> 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.</span >
I can imagine it being not a bug, but actually an intentional logic along the original behavior of not sending POST body. Where in both cases, the intent correctness can be discussed, but not treated as a bugfix. I have spent some time looking into WK2 sources, hoping to find an approximate place of such "bug". I got a gut feeling instead: when registerSchemeForCustomProtocol is invoked, things appear to get flipped to a "custom protocol" primarily on WK side and the IPC is just a subsystem. So a stripped POST request is made for that custom protocol, and when IPC pipe spits out "not interested", WK side simply goes on with the request already made. Take this with a shovel of salt, i'm a github skimmer, not WK contributor.</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>