Re: [squid-users] Re: Cosmetics: How to eliminate HTTP error msg completely ?

On 5/02/2014 4:58 p.m., babajaga wrote:
> Thanx, I did not think about the simple solution :-)
>
> However, this does not work for CONNECT. Not because of squid, but because
> of "a new standard" set by the browser developers, NOT to display proxies
> custom error message in this special case.
> Ref. here, for example:
> https://bugzilla.mozilla.org/show_bug.cgi?id=493699
>

That is only relevant for *display*. For example showing the user a
different web page in the browser.
Your question was for sending a blank (empty) reply from Squid. Which
works equally well for CONNECT as for any other status.

>
> However, as a workaround, this is suggested:
> "Note that one workaround for this is to issue a redirect (via a 302 or
> other 3xx HTTP status code) rather than a 403. Point the redirect to a URL
> for your custom error page. This will work in Firefox 3.0.12 (and 3.5RC1)
> and later."
> Will try to write another redirector now. Any trick to use 2 different
> redirectors in squid 2.7 ?

If you are writing URL-redirect helpers there is only one point at which
URL-redirect/rewrite is checked for and one result accepted back by
Squid. How you generate that result is entirly up to you. The usual
method to run multiple redirect/rewrite helpers is to simply have one
helper call the other.

On the other hand deny_info works as far back as Squid-2.6 and you can
have as many different ones as you want http_access, http_access2, and
http_reply_access lines combined.

Amos
Received on Wed Feb 05 2014 - 06:19:47 MST