On 01/23/2014 09:00 PM, Amos Jeffries wrote:
The opening up of -n is now done in trunk. Anything which needs to be
unique for the instance/service should begin to make use of the global
char* service_name as part of its uniqueness.
The above scope definition would apply to things like the
On 01/23/2014 06:23 AM, Amos Jeffries wrote:
+if (size 0) {
+if (!ignoreErrno(xerrno)) {
+debugs(5, 2, tcp read failure: xstrerr(xerrno));
+return true;
+} else if (!inBuf.hasContent()) {
+debugs(5, 2, tcp : no data to process (
On 01/22/2014 06:16 PM, Amos Jeffries wrote:
On 2014-01-22 18:45, Alex Rousskov wrote:
The correct design depends
on what our clients and servers need. I am seriously worried that you
are too focused on one server now (client_side_*cc) and once you start
adding more and more agents, the
On 01/23/2014 02:34 AM, Amos Jeffries wrote:
On 22/01/2014 10:32 p.m., Henrik Nordström wrote:
Any design that tries to make application level code (i.e. http/ftp
protocol handlers etc) needing to be aware of TcpReceiver/Sender is
plain wrong imho.
Yes. I was loosely thinking of completing
fre 2014-01-24 klockan 08:57 -0700 skrev Alex Rousskov:
Please note that since Windows admins want a service name even if they
do not run multiple single-build instances on the same box, setting that
service name should not suddenly make their life more difficult by
altering squid.conf
Hello,
I propose to limit squid.conf ftp_epsv off prohibition to IPv4 FTP
servers.
Setting ftp_epsv to off is often necessary to correctly handle
real-world cases where an IPv4 FTP server correctly responds to an EPSV
command but is located behind a firewall that does not understand EPSV
On 01/24/2014 01:11 PM, Henrik Nordström wrote:
fre 2014-01-24 klockan 08:57 -0700 skrev Alex Rousskov:
Please note that since Windows admins want a service name even if they
do not run multiple single-build instances on the same box, setting that
service name should not suddenly make their
fre 2014-01-24 klockan 14:27 -0700 skrev Alex Rousskov:
using the same Squid build (bug 3608). That bug report contains a
suggestion to make the currently ./configure-set IPC paths explicitly
configurable in squid.conf, but using service name side-effects also
works. I am not sure which
