error message "Your request is prohibited because it would cause a cycle"
When I try to go to my inbox I get the message 'Your request is prohibited because it would cause a cycle'. I've tried exiting and reloading but the same thing happens
Additional System Details
- Shockwave Flash 11.1 r102
- Google Update
- NPRuntime Script Plug-in Library for Java(TM) Deploy
- Next Generation Java Plug-in 1.6.0_29 for Mozilla browsers
- Picasa plugin
- DjVu browser plugin
- CANON iMAGE GATEWAY Album Plugin Utility Module
- Windows Presentation Foundation (WPF) plug-in for Mozilla browsers
- User Agent: Mozilla/5.0 (Windows NT 6.0; rv:10.0.2) Gecko/20100101 Firefox/10.0.2
Basically, that means if you go to your email, it would keep on looping round to the same page your on, meaning it could be an auto redirect to the same page or similar.
Dear Taddle1, maybe so, but I only get this message if i go the bookmark route to my inbox. Other routes work OK. John
It is better not to bookmark a link to go directly to pages like, but access that page in the normal way by clicking links.
Some page use hidden forms or cookies to open a specific page and a bookmark won't work in such cases.
Although I have changed nothing, I suddenly started getting this message when I try to log on to Yahoo. Yahoo support did a check and say it is my browser which is at fault. Can anyone say why and what has happened to make the error start appearing now?
This has started happening to me - both on my main computer and on my kindle - so I do not think it has anything to do with the browser.
I don't really care why Firefox is giving me this message. I just want to know how to fix it!
Do you still get that error if you start on the main page and click though the links to reach the page that you want to go to?
Yes, the only way I can access my SBC Global account is from the AT&T.net homepage. Any shortcuts or direct links other than that one fail with that message.
Shortcuts or specific links that you bookmark (a bookmark also stores POST data) may only be valid during the current session.
If you use them at a later time then they may have become invalid and in that case you get a server error.
So I't's just a coincidence that it started doing this immediately after I executed a Firefox update?