Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 155 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

When I go to the "Reputation" tab for my profile and click the "show removed posts" checkbox, the page suddenly jumps to this raw HTML/JS:

And it stays there, infinitely loading. This happens on Chrome 18.0.1025.151 m and Firefox 8.0.1, with no extensions/addons.

Any ideas why this is happening?

I am behind a proxy, but none of SE is blocked.

Maybe there's some funky cross-domain AJAX going on here?

The JS console log shows nothing.

The Network tab on the Chrome developer tool showed 1 GET and no errors. The response of the GET:

    "response": {
      "status": 200,
      "statusText": "OK",
      "httpVersion": "HTTP/0.9",
      "headers": [],
      "cookies": [],
      "content": {
        "size": 30614,
        "mimeType": "text/plain"
      "redirectURL": "",
      "headersSize": 19,
      "bodySize": 0
share|improve this question
No repro on Chrome latest. – Cody Gray Apr 11 '12 at 1:43
At a glance, I think you have a crazy proxy between you and us...any idea if that's the case? – Nick Craver Apr 11 '12 at 1:44
I am indeed behind an organization proxy, but none of SE is blocked. Strange. – JBurace Apr 11 '12 at 1:45
Norepro Chrome Canary – Manishearth Apr 11 '12 at 3:57
@JBurace: Maybe the filtering regex decided that it doesn't like headers? Strange though. – Manishearth Apr 11 '12 at 3:58
Does this work when not behind that proxy? This has been reported nowhere else...I do believe the proxy you're behind isn't setup correctly. – Nick Craver Apr 16 '12 at 22:01
To notify people of comment reply please use @ for example adding @Nick in the beginning will notify him of your comment, otherwise he will most likely miss it. – Shadow Wizard Apr 17 '12 at 8:30
@NickCraver It does outside the proxy, at a friends place etc. Everything else (Google, Bing, etc) work just fine under the proxy so everything looks fine. Not sure how it wouldn't be setup right and cause this. – JBurace Apr 17 '12 at 19:51
up vote 2 down vote accepted

When this happens, go to the Network tab of Chrome developer tools:

chrome network tab

And you will hopefully see something abnormal like error status that will shed some light on what exactly is being blocked.

share|improve this answer
I tried that and only saw 1 method "GET", which looked fine. See my post for the response of the GET. – JBurace Apr 17 '12 at 19:54
Looks like mime type issue - should be text/html not text/plain. – Shadow Wizard Apr 17 '12 at 21:04
Good point. I checked some other SE functions like "flag" and it returns text/html. Is SE sending it as text/plain, or is something on my end interfering and changing that? – JBurace Apr 17 '12 at 21:21
Your end otherwise we would have seen influx of reports... – Shadow Wizard Apr 17 '12 at 21:42

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .