This entry was posted
on Tuesday, June 14th, 2011 at 12:02 pm by Radley Balko
and is filed under Police Professionalism.
You can follow any responses to this entry through the RSS 2.0 feed.
Both comments and pings are currently closed.
Is anyone else having this problem? On multiple browsers http://www.theagitator.com only loads posts from June 8 and earlier. To see more recent posts, I have to click on June 2011 from the archive drop-down menu. Really weird.
Can we come up with a police “professionalism” bingo board? These arent even surprising any more, and you know exactly how the goddamned admin is going to handle it.
Which will it be this time? No finding of errors, paid suspension, internal policy review or big civilian payout?
Jay, it will be back. As soon as I post a comment (any little remark) on the article from the 8th and hit the home button I actually get the most recent posts. However, as soon as I close my browser–back to the beginning. I have tried multiple computers, multiple browsers, and multiple locations (home, work, coffee shop, library) all with the same results. As to the cache idea. I had my sister–who would have never gone on the Agitator site (total sheep) of her own accord–try and she also got the 8th. Hey Radley–give us a hand and have your tech guy fix this–we (many of your readers) can’t all of a sudden be doing something dumb en mass–can we?—can we? hey guys, can we?
@Jay (comment #4 above) and others – same here; it’s not a cache issue, and the same problem exists in four different browsers and on my tab as well as 3 PCs. I’ve used the tab on 3 different wifi networks and on 3G (hence, several different ISPs) so it’s not ISP-level caching.
It is almost certainly a CMS (content management system – ie, server side, backend) issue.
That said: the RSS feed (to which I subscribe) is always up to date; if you have a modern browser you can use the RSS feed link instead of the homepage link.
@Chris Rhodes – it would be staggering to me if some combination of browser, router and OS caching could yield the results we see. This box (running Ubuntu 11.04) doesn’t cache at the OS level, and nor does my router… yet I get the same behaviour for the Agitator homepage on Chrome, Chromium, Opera and Firefox.
I’ve seen this same phenomenon in the past with other sites, but never for more than two or three days (e.g., during DNS repropagation after a hosting change).
I’ve had the same browser issue and it’s a little mysterious. I can browse normally using my old Netscape 9 browser and everything is up to date, but this site’s home page is a week old using any other browser I have installed (Firefox 4 and IE 8). That makes it seems like a local page cache issue, except that 1) it doesn’t happen to Netscape 2) I’ve cleared the browser caches (and cleared my PC’s DNS cache), and 3) some many others are having the same problem.
Anyway, others having this problem might want to try a different browser. Here’s the link for Netscape 9. I don’t know about Opera, etc.
I had difficulties with the site for one day, only; I was getting the error message “this host does not exist”, then suddenly there it was and I’ve had no problem since, using Chrome on a Vista machine.
The redirect returned by the server was either missing a location or would result in a loop. The latter may happen when a site redirects users to Coral without checking (via UserAgent, for example) that the requester is not a Coral proxy itself. Please report this problem to the server if possible.