Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 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

For some reasons, I am using a localhost proxy configured as "HTTP CONNECT Tunneling". When I open anything under, I get a runtime error page.

I think this is because my proxy adds an HTTP header:


How can my problem be fixed?

share|improve this question

closed as too localized by Peter Mortensen, Martijn Pieters, amanaP lanaC A nalP A naM A, ChrisF, Rory Feb 27 '13 at 22:46

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Um. Don't use a local proxy? – Oded Feb 27 '13 at 15:46
I know the concept of a send stuff through it so that the receiving end does not see it is you, but instead only sees the proxy. But what does a local proxy do? – Time Traveling Bobby Feb 27 '13 at 15:55
@SulfurizedDemonbobby: that's only one possible use of a proxy, the technique can be used for many different gains: filtering unwanted content, anonymization (what you mentioned), "adding value" (usually ads), ensuring that rules are followed, ... – Joachim Sauer Feb 27 '13 at 16:03
@JoachimSauer: Oh yeah right, altering content on the fly...completely forgot about that, thanks. :) – Time Traveling Bobby Feb 27 '13 at 16:04
Sounds like a broken fix for the vulnerability that allowed you to access debug/admin features on SO by setting this header. – CodesInChaos Feb 27 '13 at 16:16
No repro. Either a stealth fix or your problem lies somewhere else. – a cat Feb 27 '13 at 17:22

It doesn't make sense to invest time in (and continuing supporting) this very narrow use case.

Especially since it should be possible to fix on your end, we're not going out of our way to detect proxies or anything.

share|improve this answer

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