[soup] Initialize m_soupFlags in all ResourceResponse constructors.
authorkubo@profusion.mobi <kubo@profusion.mobi@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Fri, 13 Jan 2012 18:05:41 +0000 (18:05 +0000)
committerkubo@profusion.mobi <kubo@profusion.mobi@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Fri, 13 Jan 2012 18:05:41 +0000 (18:05 +0000)
commita4af2e3134f7d55b3bbc9fa43d43252f6a9b3dde
tree8eb8266b4ef6fde00944771b3bc6cd4428800633
parentf0f5f200bfd6218be3dac8541d6f5fecefd8d7df
[soup] Initialize m_soupFlags in all ResourceResponse constructors.

Rubber-stamped by Gustavo Noronha Silva.

m_soupFlags was being initialized in two of the three ResourceResponse
constructors, causing some trouble in
FrameLoaderClient::dispatchDidReceiveResponse (ports which use
ResourceRequest::setSoupMessageFlags with the response's unitialized
flags).

* platform/network/soup/ResourceResponse.h:
(WebCore::ResourceResponse::ResourceResponse):

git-svn-id: https://svn.webkit.org/repository/webkit/trunk@104948 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Source/WebCore/ChangeLog
Source/WebCore/platform/network/soup/ResourceResponse.h