I have an network platform implementation (ResourceHandle) that I'm not sure is doing the right thing.
In particular, a.html has a <script> tag that references http://missing/missing.js. missing.js is non-existent and the response status is 404, but the response has a HTML body. When opening a.html, WebKit actually tries to parse the resource for missing.js, which is HTML, not Javascript. This behavior is probably wrong, but I don't know which component is broken, i.e. whether my network code is communicating the wrong thing to the ResourceHandleClient, or someone further up is failing to catch the bad response status and prevent parsing. So, if I get a response with 404 (or other error codes) plus a body, what does my network code need to do? Which of the did.* functions should I call? Or, is the problem further up, with ResourceLoader or something even higher? Josh
_______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
