engadget does a HTTP 307 temporary redirect to the site. ublock inserting its warning page leads to a security context switch to an extension page which trigger

engadget does a HTTP 307 temporary redirect to the site. ublock inserting its warning page leads to a security context switch to an extension page which triggers a dev tools reload which in turn removes the request history. You can view the requests in the global browser console instead. Presumably the ad would direct you back to engadget once you click or something and add a parameter to prevent an infinite redirect loop.