When creating a WebCore object from a SoupMessage, we are not storing the message flags anywhere, so they get lost, and are not restored when creating the message from the WebCore object. We need this so that apps can use the flags when they get the message from WebKitNetworkRequest.
Created attachment 49006 [details] proposed fix This is the WebKit piece of the puzzle to get information regarding SSL certs to Epiphany. Although this was the primary motivation, this is indeed a limitation of the backend in general, and has potential to be useful in other cases.
Created attachment 49086 [details] Refactor updating of ResourceResponse
Created attachment 49087 [details] Fix the actual problem Patches split, as discussed by Jabber =).
Comment on attachment 49086 [details] Refactor updating of ResourceResponse The ChangeLog seems a bit... unorthodox. Otherwise looks fine.
Comment on attachment 49087 [details] Fix the actual problem LGTM.
Comment on attachment 49086 [details] Refactor updating of ResourceResponse Landed as r55046.
Comment on attachment 49087 [details] Fix the actual problem Landed as r55047.
Comment on attachment 49087 [details] Fix the actual problem I had to roll this out because it caused tests to fail, but I figured out the problem (I was failing to initialize m_soupFlags to 0 when constructing the objects), and got Xan to do an informal rubber stamp, and then relanded.