Amos Jeffries wrote:
You were right. The invalid reply header problem doesn't happen when using 3.0.stable20, only 19. I'm still working on the 404's. I must be doing something wrong somewhere. I have found a few more dumb things in my config (aka, multiple snmp_port lines) but the going is slow. We're really busy here at the shop, and my computer is the only one running ubuntu, so it's not a priority. I'll post back when I get this resolved.Matthew Morgan wrote:Matthew Morgan wrote:Are there any known issues with squid 3.x and apt-get update on Ubuntu? On 2.7 everything worked fine, but on 3.0-stable19 and 3.0-stable20, I get random 404 responses when doing apt-get update. I tried starting with a fresh cache, but no dice. Here's my squid.conf:Quick note: the errors are not always 404's. Sometimes they are like: Err http://us.archive.ubuntu.com jaunty Release.gpg The HTTP server sent an invalid reply header [IP: 91.189.88.45 80]You may be encountering the remains of bug #7. Or some upstream provider with bug #2624 (fixed in 3.0.stable20).If you can track down what that invalid reply header is and whether its coming into Squid from the web server would be a great help.Amos
