Re: Squid 1.2 & Error Messages

Agreed. And I feel the same way. I just don't see any particular way of doing it
that's not more trouble than it saves. The best way, IMO, is to make 1.2 really
kick-ass and SOLID. Then encourage our ancestors up the tree to switch to it
when it is.

D

Jordan Mendelson wrote:

> > Oh, it's _doable_, but I imagine that you'd want to change the error
> protocol
> > somewhat (which means it's not comfortably backwards compatible with 1.0
>
> The main problem is that custom error messages are completely useless with
> 90% of my error messages come from nlanr parent caches.
>
> I mean, the default error messages are about as bland as possible and
> frankly, none of my users understand them. Plus, I'd like to attach links to
> our help pages for more information, add a company logo, etc. I can do this
> with custom error messages, it's just that they don't show up when
> xx.cache.nlanr.net can't get somewhere.
>
> Jordan

--
Did you read the documentation AND the FAQ?
If not, I'll probably still answer your question, but my patience will
be limited, and you take the risk of sarcasm and ridicule.