Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

After some research, I finally managed to apply our company's blocked sites list to https/ssl websites using a "deny CONNECT" acl.

However, when a user tries to access a blocked website, he only sees the default 503 error page from his browser, instead of our standard access denied page.

Is there anyway to configure SQUID to display an error page instead of the browser's error page ?

share|improve this question
I think it's the browser's choice. It's not up to Squid. – yarek Mar 1 '12 at 15:00

To clarify the question, you are having problems with HTTPS sites?

I am currently investigating how to make it happen as well. Squid in the middle (breaking ssl) is an option, but one I don't want to take yet.

I split ours into two files and acl until this can get resolved. I use this for https:

deny_info TCP_RESET acl

It will not tell them to try to change network proxy settings, just saying it network connection reset.

share|improve this answer
Yes, its with HTTPS websites. For the time being, I'm using always_direct until we get our hands on our new FW solution. – T. Fabre Nov 20 '12 at 16:10

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.