Hmm, now that I look again, the docs appear to have magically changed on me, I must have accidentally looked at a 2.7 doc. Ok, great, the bug report's there and I've been able to work around any non ported features in 3.2 now (urlgroups as one, but that wasn't a stopper for me). I'm going to start running 3.2 beta through some testing using digest authentication (w/ custom helper), logdaemon, and a url_rewriter. Let me know if there any particular areas that I should focus on that might help flush things out? And thanks for all the help and great work! David -----Original Message----- From: Henrik NordstrÃm [mailto:henrik@xxxxxxxxxxxxxxxxxxx] Sent: Tuesday, September 21, 2010 1:50 AM To: David Parks Cc: squid-users@xxxxxxxxxxxxxxx Subject: RE: Interminted TCP_DENIED mÃn 2010-09-20 klockan 18:27 -0700 skrev David Parks: > I was not able to reproduce the intermittent 407 problem in this version as predicted by Amos. > > However I did run into some other issues: > 1) A bug with digest authentication - > Open a browser and authenticate. Now restart squid (don't close the browser) > Try browsing to another page. This crashes squid with the following error in squid.out: > "FATAL: Received Segment Violation...dying." PLease file a bug report on this if you have not already. http://bugs.squid-cache.org/ > 2) Question: Is url_rewrite_concurrency gone? I get a config file warning that it's not recognized. > But it's in the squid.conf.documented docs as valid. are you sure the squid.conf.documented you are reading is from the right version? My 3.2 copy do not mention url_rewrite_concurrency The concurrency level is set in url_rewrite_children these days. Regards Henrik
