What is the status of this now? If this bug still exists, this makes it hard to use on LANs with several users, as a few are likely to have repositories not cached by the proxy. The beauty of squid-deb-proxy seems to be that it needs no client-side configuration - if the administrator sends mails to people on the LAN (who might be non- technical users) saying "if you have blah blah blah, please edit such and such configuration file", it really spoils things. Some things like Dropbox and the Google Talk plugin automatically add repositories, and a non-technical user may not even know what a repository is! squid-deb- proxy should _just work_ for the clients.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/545830 Title: 403 error when using a non-cached repository To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/545830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
