Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

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?

share|improve this question

migrated from webapps.stackexchange.com Aug 23 '13 at 10:55

This question came from our site for power users of web applications.

add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.