| 10:00 pm on Nov 2, 2011 (gmt 0)|
I'll assume no one else has a problem, then. :)
| 4:41 am on Nov 3, 2011 (gmt 0)|
I mainly use Opera for WebmasterWorld. I just tried it with FF and NoScript and didn't notice this behavior. Looked normal to me.
| 4:58 pm on Nov 3, 2011 (gmt 0)|
I use FF plus NoScript for browsing and I do not see this issue either. I do have WebmasterWorld in my WhiteList though too.
| 10:28 pm on Nov 3, 2011 (gmt 0)|
Hadn't thought of whitelisting...
... hmm. Didn't make a difference but perhaps I need to re-start FF first. I'll report back later.
| 2:16 am on Nov 4, 2011 (gmt 0)|
Could it be another Add-on?
| 4:16 am on Nov 4, 2011 (gmt 0)|
For a period of time it did that for me... then after I upgraded my FF it quit. What version of FF are you running?
| 10:11 pm on Nov 4, 2011 (gmt 0)|
It did it under 3.6 until a few weeks ago. After I added FF Stable to my repository it updated to 7 and still got the same problem. Whitelisting hasn't made a difference.
The message, paraphrased, is "Firefox prevented redirect". I click Allow and it reloads correctly.
| 9:37 am on Nov 23, 2011 (gmt 0)|
If you create a new profile does it give you the same warning?
| 10:40 pm on Nov 23, 2011 (gmt 0)|
Haven't tried that - I only run a single profile - but thanks for the tip: I'll check it out.
Looking at an auto-updated page of a router's status, it looks as if this is a function of the header's meta redirect. I began looking at a manual a few days ago but time ran out on me. :(