Quote:
Originally Posted by SelfProtection
I have a question about Web Browser Operation.
What Really happens when a Browser receives a 307 relocate request & the relocated Site is blocked either in the Hosts File or a Firewall?
Does the Browser repeat the request for the Original WebSite or retry on the 307 relocate, if it is the Original Website then the Webwise System may have a real problem; how do they stop looping if the cookie option is no longer being used to test for it?
I was wondering whether this could be the cause of many reports of Routers re-syncing & more rst commands in the past couple of weeks?
|
If you block webwise.net etc in your host file so that it points to 127.0.0.1 then the redirect will try and access that and it will end there. Depending on your browser you will either get a message that the page is not available or a blank page. Effectively it will stop your browsing stone dead, you will go nowhere, it will not retry. You will get a similar effect if you try blocking in your software firewall.
It has nothing to do with routers resynching though, they will be doing this because you have a noisy line or whatever. Phorm hopefully has no way of resetting your router...