Curious issues with Balloon-Juice.

Post #321,268 by Another Scott 2/10/10 10:49:19 AM Reply	Curious issues with Balloon-Juice. On February 8 I suddenly was unable to see content at http://www.balloon-juice.com but things worked fine with http://www.balloon-juice.com/index.html I sent John an e-mail, and he put up this post - http://www.balloon-juice.com/?p=34325 Some other posters said the problem went away when they cleared their cache (didn't help me), and some said it seemed to be a cookie issue that was reset when they posted (I've never posted there). Some posters are seeing the exact same things I am (just a blank white page). This morning, the .../index.html "trick" doesn't work, but http://www.balloon-juice.com/?paged=1 does. Needless to say, since http://www.balloon-juice.com still doesn't work, the problem seems to be getting worse. I see the same thing with FF3.6, Safari, and on WinXP and Kubuntu. Could it be some sort of DNS or ISP caching issue? Is someone stealing the traffic? It seems very strange.... Thanks. Cheers, Scott.
Post #321,270 by jake123 2/10/10 11:44:11 AM Reply	I can tell you that it works fine here fwiw.
Post #321,291 by Another Scott 2/10/10 6:02:59 PM Reply	Thanks. Anyone else? It's still busted here.
Post #321,296 by scoenye 2/10/10 7:26:05 PM Reply	Totally busted for me Neither URL works. I get totally empty pages in Firefox. Wireshark shows the GET going out, the HTTP 200 reply comes back with 0 length, and FF then shuts down the connection. Clearing the cache did not help. Doing the same with Konqueror gets a bit further, but it is still messed up. The first request has the same result as on FF, but Konqueror then tries to grab favicon.ico. The server responds to that with the HTML main page (which gets ignored because text/html wasn't in the list of MIME types in the request). Following the Konqueror try, a manual attempt to grab the CSS sheet in FF also returned the entire main page HTML which it proceeds to render in full. One odd thing I noticed in the returns is that the page was being returned from a server side cache, with a 02/08 timestamp.
Post #321,299 by Another Scott 2/10/10 7:47:58 PM Reply	It does seem very strange, but on their end, somehow. The latest fix seems to involve posting and getting a cookie back. http://www.balloon-j...4#comment-1579358 The people who are having success are obviously posting. Except for Jake, maybe? Thanks. Cheers, Scott. (Who is glad he doesn't have his own site and hasn't been at the mercy of gremlins like these...)
Post #321,319 by jake123 2/11/10 9:33:17 AM Reply	I in fact do post there from time to time polyorchnid octopunch being the handle I use.
Post #321,321 by Another Scott 2/11/10 9:43:23 AM Reply	Ah! :-) So it all fits. Thanks.
Post #321,302 by Andrew Grygus 2/10/10 8:12:20 PM Reply	Puts up a blank page and says "Done" here.
Post #321,305 by Another Scott 2/10/10 8:37:40 PM Reply	Seems to be another "FYWP" attack. FYWP = "Fuck You WordPress". http://www.balloon-j.../?page_id=28596#F In paraticular: http://www.balloon-j...4#comment-1579527 From the wp-super-cache docs: WP Super Cache ... This plugin generates static html files from your dynamic WordPress blog. After a html file is generated your webserver will serve that file instead of processing the comparatively heavier and more expensive WordPress PHP scripts. ... The static html files will be served to the vast majority of your users, but because a userÂs details are displayed in the comment form after they leave a comment those requests are handled by PHP. Static files are served to: ... 1. Users who are not logged in. 2. Users who have not left a comment on your blog. 3. Or users who have not viewed a password protected post. I think we have a culprit Thanks, all. Cheers, Scott. (Who understands WordPress is one of the most popular blog frameworks... :-/ )
Post #321,331 by Another Scott 2/11/10 2:03:03 PM Reply	They upgraded Wordpress. It seems Ok now. http://www.balloon-j...te-maintenance-5/ Cheers, Scott.

Welcome to IWETHEY!