Step to reproduce: 1. Go to http://www.nifty.com/ with a mobile User Agent Expected: Stays on http://www.nifty.com/ (if a flag to disable redirections existed) Actual: Redirected to http://www.nifty.com/smp/?top There are many ways to redirect a page to a new context: HTTP: 301, 302, 307, with a `Location:` header JavaScript: with a `window.location` HTML: with a meta refresh It would be very useful to be able to 1. block completely the automatic transition context to a new location. 2. an/or go through a step by step navigation. In the Network UI panel you would get the possibility to switch from one context to the other for the main context (HTML) Some issues in terms of UX: * what's happening for the redirection done for each individual files such as images, js, css, etc. triggered by the main context. These could be useful for the analysis of the main context. Why is it useful? Sometimes when debugging, specifically in the case of User agent sniffing and initialization, we need to be able to understand the context before such as setting breaking point etc. But when the automatic redirections happen, it's not possible to do that anymore. In the case of client side, disabling JavaScript doesn't help. See Bug 1234426