We are using Squid 3.0 as a reverse proxy for our app. I ran into a
situation where the entity in some messages does come through the
cache cleanly. I added this information to bug 897:
http://www.squid-cache.org/bugs/show_bug.cgi?id=897
(comment #8 and #9)
I now have a larger repeatable test case where the entity is
significantly changed as it passes through Squid. Both situations
involve XML files (HR-XML fwiw).
I have the captured the HTTP message in it's pre-squid form, and I can
send this through Squid to repeat the problem and see the results just
using some socket tools in my develpment environment.
I wondered if this test case would be useful ... I can send along the
test pre-squid message (and the post-Squid I get with the version we
have here) to anyone interested in it/them. I have not attached them
here because the messages are each ~500KB in size.
I am not a C developer myself, and the version of Squid 3.0 we use was
packaged for us for Debian Woody by a kind voluteer. It would be
wonderful for us to know if the problem we are seeing is resolved in
the more recent Squid 3.0 versions before we prevail upon our
volunteer again. Alternatively, if some kind person had a recent
build of Squid 3.0 packaged for either Debian Woody or Sarge, I would
be happy to run my tests against that and report back here.
Thank you for your kind attention,
Bruce
--
Make the most of your skills - with OpenSkills
http://www.openskills.org/
