ResourceResponse does not have any clear way to keep platform response and WebCore data in sync. Calling any setter on the response leaves these in inconsistent state.
Furthermore, even if NSURLRequest was originally null, building it from WebCore data is extremely lossy - we don't even use a correct HTTP status code, defaulting to 0.
WebKit2 IPC only encodes NSURLRequest, so the other side will see a bad response with 0 status code for anything that was built synthetically (including but not limited to Blob reading responses).
Until rebuilding an NSURLRequest from platform data is implemented (and that's non-trivial), we'll have to send both over IPC.
Created attachment 191833 [details]
> Furthermore, even if NSURLRequest was originally null...
> WebKit2 IPC only encodes NSURLRequest...
>Until rebuilding an NSURLRequest from platform data is implemented ...
Did you mean NSURLResponse in each of these sentences?
Comment on attachment 191833 [details]
Not a fan of the huge swath of new fixmes without a bug #, but I think this is fine.
> Did you mean NSURLResponse in each of these sentences?
Thank you for reviewing!