commit 56cfc011f33473aca83b7dba839e84058f61b7f4
author commit-queue@webkit.org <commit-queue@webkit.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc> Thu Jan 12 23:12:13 2017 +0000
committer commit-queue@webkit.org <commit-queue@webkit.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc> Thu Jan 12 23:12:13 2017 +0000
tree b82ec506722229e9ed893e3c8389bd11ce54e3c5
parent 78127c1770bc3bbc2c155eed1f3e61d69125b0c0

Make ApplicationCacheHost::maybeLoadSynchronously more robust
https://bugs.webkit.org/show_bug.cgi?id=165192

Patch by Youenn Fablet <youenn@apple.com> on 2017-01-12
Reviewed by Alex Christensen.

No change of behavior.
Currently, in case out parameter "data" is not null and shouldLoadResourceFromApplicationCache returns false and resource is null, we might dereference a null pointer when calling maybeLoadSynchronously.
We refactor the code to ensure that this case cannot happen anymore.

* loader/appcache/ApplicationCacheHost.cpp:
(WebCore::bufferFromResource):
(WebCore::ApplicationCacheHost::maybeLoadSynchronously):

git-svn-id: http://svn.webkit.org/repository/webkit/trunk@210682 268f45cc-cd09-0410-ab3c-d52691b4dbfc