summaryrefslogtreecommitdiffstats
path: root/chrome/worker/webworkerclient_proxy.h
diff options
context:
space:
mode:
authordarin@chromium.org <darin@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-08-06 20:08:47 +0000
committerdarin@chromium.org <darin@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-08-06 20:08:47 +0000
commitc24d79d0a8a0e3dba8891358709f2ab3eb781f16 (patch)
tree19a3f1633e27549d059d8e598a5c93ef497477ee /chrome/worker/webworkerclient_proxy.h
parent03c67253ed58e18896f27f95774349bf86000e7f (diff)
downloadchromium_src-c24d79d0a8a0e3dba8891358709f2ab3eb781f16.zip
chromium_src-c24d79d0a8a0e3dba8891358709f2ab3eb781f16.tar.gz
chromium_src-c24d79d0a8a0e3dba8891358709f2ab3eb781f16.tar.bz2
With our posix TCP implementation, attempting to load an URL with IP address
255.255.255.255 results in ERR_ADDRESS_UNREACHABLE whereas on Windows it results in ERR_ADDRESS_INVALID. Map both of these errors to the same value of -1004 for the sake of matching the layout test behavior of WebKit for the Mac. This may also fix ChromiumMac, but I haven't tested it there yet. R=dglazkov BUG=18665 TEST=none Review URL: http://codereview.chromium.org/165077 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@22651 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/worker/webworkerclient_proxy.h')
0 files changed, 0 insertions, 0 deletions