Fix problems with PPB_URLLoader_Impl and PPAPITests.URLLoader.

webkit/plugins/ppapi/ppb_url_loader_impl.cc

Index: webkit/plugins/ppapi/ppb_url_loader_impl.cc
===================================================================
--- webkit/plugins/ppapi/ppb_url_loader_impl.cc	(revision 88604)
+++ webkit/plugins/ppapi/ppb_url_loader_impl.cc	(working copy)
@@ -475,8 +475,10 @@
 
 void PPB_URLLoader_Impl::didFail(WebURLLoader* loader,
                                  const WebURLError& error) {
-  // TODO(darin): Provide more detailed error information.
-  done_status_ = PP_ERROR_FAILED;
+  // If a URL load fails, return PP_ERROR_NOACCESS instead of the more generic
+  // PP_ERROR_FAILED. There is no simple concept of error codes in the
+  // underlying WebKit loader framework.
+  done_status_ = PP_ERROR_NOACCESS;

[darin (slow to review), 2011/06/11 05:13:12]

Well, the error codes actually are defined by Chromium.  In particular, most
error codes come from the underlying WebURLLoader implementation that lives in
Chromium.  I'm sure we can interpret those here.

Perhaps you sometimes see error codes that do not have domain set to
net::kErrorDomain?  In that case, maybe it makes sense to map those to
PP_ERROR_NOACCESS?

Please also note that for error codes used by WebCore that are not generated by
the network stack, WebCore::FrameLoaderClient methods are called to get access
to them:  e.g., cancelledError, blockedError, cannotShowMIMETypeError, etc.

   RunCallback(done_status_);
 }