I have a page with an external resource coming from www.googleadservices.com. Sometimes this resource takes an excessive amount of time to load, and since it is irrelevant to the part I am testing, I put an entry in my /etc/hosts to short circuit requests to 127.0.0.1.
For some reason, in Chrome (v29), the browser never sees the request as completed. If I look in the developer tool, under network, it shows a status for the request as "404", but shows the time as still "pending". This is causing problems for Selenium tests, that can't move on to the next step until the first step sees the page as "completed" loading.
Is there some reason why Chrome doesn't consider a 404 a final response? Is there any way to force Chrome to treat a 404 as a final response?