[SQU] refresh_pattern, aka dealing with an arrogant consultant

Hello,

I have a problem with a consultant accusing me of misconfiguring squid.

The problem is that some dynamic files (.swf) are not refreshed from some
website often enough, even if a user behind squid presses reload.
I found out, that the website in question does not send expire headers,
nor no-cache pragma's.

I told him this should be solved on the webserver side (they made this site
themselves), and send them a macromedia advisory.
He tells me the following:

(I censored the part where he was bragging about have been working
at a lot of fortune 500 companies, and where he was trying to make fun of the
fact that we put three hours of work in it: "this took you THREE hours?")

  It's a fact that many webdesigners do not handle dynamic pages correctly
  so every proxy has an option to always check if a new page is available
  before serving the page from the cache. It generates more traffic, and
  slows things down, but everybody uses this. MSproxy has that, Winproxy has that.
  You configured squid, it's a proxy misconfiguration, so we won't pay you for
  repairing this.

I originally did not put refresh_pattern in the squid.conf because I thought
the default would suffice, now I did.

But, is he right about proxy servers having this option, and about the fact
that everybody has this switched on?

Is this the reload_into_ims option? The docs say 'Enabling this feature could
make you liable for problems which it causes.'. What problems are meant here?

Thanks,
Ron Arts

--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html