On 9/24/2012 11:46 AM, Amos Jeffries wrote:
Haven't heard anything about this is a while. How is this project going?
Well it's holidays here now so I took a small stop to breath.
we had one just ended and 2\3 in the way so it leaves small amount of time.
and some family stuff on the way so I
On 10.09.2012 04:56, Eliezer Croitoru wrote:
On 09/06/2012 03:58 AM, Amos Jeffries wrote:
I don't think there is anything which needs new cache_cf.cc code.
The parsing side if things is identical for url_rewrite_*. The
different defaults and locations are all coded in cf.data.pre ... yes
ind
On 09/06/2012 03:58 AM, Amos Jeffries wrote:
I don't think there is anything which needs new cache_cf.cc code. The
parsing side if things is identical for url_rewrite_*. The different
defaults and locations are all coded in cf.data.pre ...
yes indeed but the actual effect comes from the code
On 9/09/2012 4:19 a.m., Alex Rousskov wrote:
On 09/07/2012 09:13 PM, Amos Jeffries wrote:
Also, any revalidation requests done later must be done on the
original request URL. Not the stored URL nor the potentially different
current client request URL.
This sounds like a very important point th
On 09/08/2012 01:36 AM, Alex Rousskov wrote:
On 09/07/2012 01:32 PM, Eliezer Croitoru wrote:
On 09/07/2012 05:10 PM, Alex Rousskov wrote:
I am not sure what "option" you are referring to in the above. The
Store::get(key) API I have described is not optional -- it is the
primary w
On 09/07/2012 09:13 PM, Amos Jeffries wrote:
> Also, any revalidation requests done later must be done on the
> original request URL. Not the stored URL nor the potentially different
> current client request URL.
This sounds like a very important point that could justify storing the
original requ
On 6/09/2012 11:00 p.m., Eliezer Croitoru wrote:
I had a *smalll* issue with my storage so I'm forced to start from
almost scratch.
I previously worked on the 3.2.1 latest stable sources and I am
wondering on where to start now?
start on head? stable?
Eliezer
3.HEAD please.
Amos
On 8/09/2012 7:38 a.m., Eliezer Croitoru wrote:
On 09/07/2012 05:10 PM, Alex Rousskov wrote:
I am not sure what "option" you are referring to in the above. The
Store::get(key) API I have described is not optional -- it is the
primary way of detecting a hit.
+1 to use the api.
are we t
On 09/07/2012 01:32 PM, Eliezer Croitoru wrote:
> On 09/07/2012 05:10 PM, Alex Rousskov wrote:
>
> I am not sure what "option" you are referring to in the above. The
> Store::get(key) API I have described is not optional -- it is the
> primary way of detecting a hit.
>
> +1 to use the
On 09/07/2012 05:10 PM, Alex Rousskov wrote:
I am not sure what "option" you are referring to in the above. The
Store::get(key) API I have described is not optional -- it is the
primary way of detecting a hit.
+1 to use the api.
are we talking about the "Store::Root().get" ?
I was just
On 09/07/2012 06:20 AM, Eliezer Croitoru wrote:
> On 09/06/2012 09:04 PM, Alex Rousskov wrote:
>> The biggest question for me is why Squid2 code was storing multiple
>> URLs with the cached object (if it was).
>> Why cannot Store just work with the [rewritten] URL given to it and
>> ignore the fac
On 09/06/2012 09:04 PM, Alex Rousskov wrote:
On 09/05/2012 06:58 PM, Amos Jeffries wrote:
FWIW, I have not reviewed the store_url_rewrite code in Squid2 so I
cannot answer the questions related to how it was done.
I can suggest ways of doing this in Squid3, but since somebody already
investigat
On 09/05/2012 06:58 PM, Amos Jeffries wrote:
> On 06.09.2012 11:58, Eliezer Croitoru wrote:
> We can pause there for the infrastructure to look fine before moving on
> to the store details. I've been waiting on assistance from Henrik or
> Alex on that for a while. They are the ones who know the ans
I had a *smalll* issue with my storage so I'm forced to start from
almost scratch.
I previously worked on the 3.2.1 latest stable sources and I am
wondering on where to start now?
start on head? stable?
Eliezer
On 9/6/2012 4:37 AM, Amos Jeffries wrote:
On 06.09.2012 13:23, Eliezer Croitoru wrote:
OK,
it seems we are getting to somewhere.
i know how to patch using command but what are the proper one to get
a patch file to be run later? will look into it.
If you are using diff:
diff -u orig_code/ n
On 06.09.2012 13:23, Eliezer Croitoru wrote:
OK,
it seems we are getting to somewhere.
i know how to patch using command but what are the proper one to get
a patch file to be run later? will look into it.
If you are using diff:
diff -u orig_code/ new_code/ >output_file.patch
If you are usin
OK,
it seems we are getting to somewhere.
i know how to patch using command but what are the proper one to get a
patch file to be run later? will look into it.
Eliezer
On 9/6/2012 3:58 AM, Amos Jeffries wrote:
On 06.09.2012 11:58, Eliezer Croitoru wrote:
On 9/5/2012 9:56 AM, Eliezer Croitor
On 06.09.2012 11:58, Eliezer Croitoru wrote:
On 9/5/2012 9:56 AM, Eliezer Croitoru wrote:
any leads,?
Well there is a nice progress.
I reviewed the 2.7 store_url_rewrite and I divided the task into more
detailed smaller tasks.
FTR: squid-2.7 ports are exempted as suitable in most cases for
b
On 9/5/2012 9:56 AM, Eliezer Croitoru wrote:
any leads,?
Well there is a nice progress.
I reviewed the 2.7 store_url_rewrite and I divided the task into more
detailed smaller tasks.
1. Research the url_rewrite interface code and Introduce a modified
version of url_rewrite as url_store_rewri
On 9/5/2012 8:00 AM, Amos Jeffries wrote:
On 5/09/2012 4:10 p.m., Eliezer Croitoru wrote:
I'm reading some code (will take a while) to maybe get a functional
store_url_rewrite for squid3+.
Actually i was thinking about it a lot and the process should be very
simple:
use some stdin+stdout like f
On 5/09/2012 4:10 p.m., Eliezer Croitoru wrote:
I'm reading some code (will take a while) to maybe get a functional
store_url_rewrite for squid3+.
Actually i was thinking about it a lot and the process should be very
simple:
use some stdin+stdout like for url_rewrite interface for starter.
I'm reading some code (will take a while) to maybe get a functional
store_url_rewrite for squid3+.
Actually i was thinking about it a lot and the process should be very
simple:
use some stdin+stdout like for url_rewrite interface for starter.
i think this is can be done pretty fast if someone
ections (all busy). The only performance
benefit arose out of servicing few busy connections when many were idle.
As for the realism or effectiveness in the real world it may be
negligible. However there are situations when a connection is idle: when
waiting for a proxy to fetch a page fr
On 10/13/2010 04:21 AM, Peter Payne wrote:
BENCHMARKS
Firstly, I wanted to address the benchmark questions as it made me
curious as to whether there really was an advantage in using /dev/poll.
I used the Apache Bench tool (that comes with HTTPD) to do my benchmarks.
I compiled a 32-bit Solaris
.
Regards
Henrik
The rest being minimal basic plumbing. I'm taking this as a second vote. :)
Applied to Squid-3 as r10946. Thank you Peter.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.8
Beta testers wanted for 3.2.0.2
ons 2010-10-13 klockan 22:25 + skrev Amos Jeffries:
>
> +1 from me with merge tweaks.
>
> Unless anyone has objections I will commit with tweaks at the next
> opportunity.
No objection from me. But have not reviewed the changes outside
comm_devpoll.cc.
Regards
Henrik
On Wed, 13 Oct 2010 15:40:22 +0100, Peter Payne
wrote:
> Hello Amos,
>
> apologies to the dev list for what must appear to be spamming.
>
Completely on topic. No apologies needed.
> Please use the attached version of the file. It has a minor performance
> tweak (only set events that have chan
ons 2010-10-13 klockan 15:40 +0100 skrev Peter Payne:
> Hello Amos,
>
> apologies to the dev list for what must appear to be spamming.
No apologies needed. We are all for release early an often, and
discussing code is what this list is for.
Regards
Henrik
Hello Amos,
apologies to the dev list for what must appear to be spamming.
Please use the attached version of the file. It has a minor performance
tweak (only set events that have changed if not clearing any events).
Compiled using CC=/tool/sunstudio12/bin/cc and tested again using Apache
B
Hello Amos,
in response to your comments.
BENCHMARKS
Firstly, I wanted to address the benchmark questions as it made me
curious as to whether there really was an advantage in using /dev/poll.
I used the Apache Bench tool (that comes with HTTPD) to do my benchmarks.
I compiled a 32-bit Sol
On Mon, 11 Oct 2010 14:58:34 +0100, Peter Payne
wrote:
> Hello Amos,
>
> thank you for your response. Please find attached the four files in
> question.
>
> Companies to mention as sponsors are BBC (UK), Siemens IT Solutions and
> Services (UK).
>
> Credit to Peter Payne, Pirosa Limited UK (n
Hello Amos,
thank you for your response. Please find attached the four files in
question.
Companies to mention as sponsors are BBC (UK), Siemens IT Solutions and
Services (UK).
Credit to Peter Payne, Pirosa Limited UK (no e-mail please).
Squid bug 3057 was raised by another member of Siem
On 08/10/10 23:13, Peter Payne wrote:
Dear Mailing List,
I have a contribution to make, a C++ file (and autoconf patches) for
/dev/poll Solaris support, ported from Squid-2 and in use on the BBC
(UK) estate managed by Siemens UK with permission from the BBC to
publish to the Squid open-source pr
Dear Mailing List,
I have a contribution to make, a C++ file (and autoconf patches) for
/dev/poll Solaris support, ported from Squid-2 and in use on the BBC
(UK) estate managed by Siemens UK with permission from the BBC to
publish to the Squid open-source project.
I've not contributed to an
Joaquim Pedro França Simão wrote:
I read a while ago that this would only be available in squid 3.2, but
wonder if there is already some implementation because I was thinking
about doing that but was wondering if there is already some effort.
It was planned to be ported along with the other 2.
I read a while ago that this would only be available in squid 3.2, but
wonder if there is already some implementation because I was thinking
about doing that but was wondering if there is already some effort.
--
osmano807
Joaquim Pedro
Hello,
HTTP compliance results for Squid 3.0.23, 3.1.16, and trunk r10264
have been uploaded to http://wiki.squid-cache.org/Features/HTTP11
We tried to preserve the old results intact for this update and just
added new stuff. Going forward, we will polish the spreadsheet and
probably remove o
On 01/28/2010 06:34 AM, Amos Jeffries wrote:
> Robert Collins wrote:
>> On Wed, 2010-01-27 at 22:49 -0700, Alex Rousskov wrote:
>>
>>
>>> c) Co-Advisor currently only tests MUST-level requirements. Old Robert's
>>> checklist contained some SHOULD-level requirements as well. I see that
>>> Sheet1 on
On 01/28/2010 04:42 PM, Mark Nottingham wrote:
> FWIW, I have an XSLT stylesheet that can format the results
> pleasantly; it could be a starting point for something automated.
Please share if you can.
Thank you,
Alex.
> On 29/01/2010, at 12:34 AM, Amos Jeffries wrote:
>
>> Robert Collins wro
FWIW, I have an XSLT stylesheet that can format the results pleasantly; it
could be a starting point for something automated.
On 29/01/2010, at 12:34 AM, Amos Jeffries wrote:
> Robert Collins wrote:
>> On Wed, 2010-01-27 at 22:49 -0700, Alex Rousskov wrote:
>>> c) Co-Advisor currently only test
Robert Collins wrote:
On Wed, 2010-01-27 at 22:49 -0700, Alex Rousskov wrote:
c) Co-Advisor currently only tests MUST-level requirements. Old Robert's
checklist contained some SHOULD-level requirements as well. I see that
Sheet1 on the spreadsheet has SHOULDs. Are we kind of ignoring them (and
On Wed, 2010-01-27 at 22:49 -0700, Alex Rousskov wrote:
> c) Co-Advisor currently only tests MUST-level requirements. Old Robert's
> checklist contained some SHOULD-level requirements as well. I see that
> Sheet1 on the spreadsheet has SHOULDs. Are we kind of ignoring them (and
> Sheet1) for now,
On 01/09/2010 04:10 AM, Amos Jeffries wrote:
> Alex Rousskov wrote:
>> On 09/12/2009 05:36 AM, Amos Jeffries wrote:
>>> Updating the checklist today I again wonder if we can repeat the step
>>> from 2.7 and enable HTTP/1.1 on requests sent to servers
>>>
>>> As far as I can see the missing bits 3.2
Alex Rousskov wrote:
On 09/12/2009 05:36 AM, Amos Jeffries wrote:
Updating the checklist today I again wonder if we can repeat the step
from 2.7 and enable HTTP/1.1 on requests sent to servers
As far as I can see the missing bits 3.2 needs to take that step are:
- reject http-Upgrade requests
On 09/12/2009 05:36 AM, Amos Jeffries wrote:
> Updating the checklist today I again wonder if we can repeat the step
> from 2.7 and enable HTTP/1.1 on requests sent to servers
>
> As far as I can see the missing bits 3.2 needs to take that step are:
>
> - reject http-Upgrade requests from client
trying to fix bug 2176 I think I see a
clean way to create expect-100 handling in Squid-3.
If someone with more store experience can point out to me how to reset
the StoreEntry properly after receiving and passing on a reply we can
accept and process the 100 reply and then reset it for the actual
>
>> skipping the HTTP/1.0 version override on
>> non-HTTP protocol replies.
>
> Right.
>
> What Squid-2 does is to add that header internally with HTTP/0.9 as
> version. The version is overridden anyway when the response is composed.
Aye. I read the patch man
mån 2009-11-02 klockan 00:43 +1300 skrev Amos Jeffries:
> Since we have no central place where the headers are upgraded I've had
> to skip porting the upgrade_http0.9 hack in Squid-2 and go straight to
> accepting ICY protocol as an accepted response protocol and handling it.
What do you mean by
Amos Jeffries wrote:
Since we have no central place where the headers are upgraded I've had
to skip porting the upgrade_http0.9 hack in Squid-2 and go straight to
accepting ICY protocol as an accepted response protocol and handling it.
Somewhat primitive for now. It's limited to parsing and re
Since we have no central place where the headers are upgraded I've had
to skip porting the upgrade_http0.9 hack in Squid-2 and go straight to
accepting ICY protocol as an accepted response protocol and handling it.
Somewhat primitive for now. It's limited to parsing and regenerating the
status
Hi Henrik,
Sorry again for the delay ... :-(
>
> > c:\work\vc_string\vs_string.cc : see declaration of 'size_t'
> > c:\work\vc_string\vs_string.cc(34) : error C2057: expected constant
> > expression
>
> Good. so it seems the test case worked.
>
> now replace std with testcase and try a
tor 2009-09-17 klockan 11:15 +0200 skrev Guido Serassio:
> It fails:
>
> vs_string.cc
> c:\work\vc_string\vs_string.cc(1) : error C2371: 'size_t' :
> redefinition; different basic types
Gah, should have been unsigned long.. but interesting that VS apparently
has size_t built-in. It was declared
Hi Henrik,
>
> Odd... std::string::npos is declared as follows:
>
> namespace std;
>
> template class _Traits,
> class _Ax>
> class basic_string
> : public _String_val<_Elem, _Ax>
> {
> public:
> static const size_type npos;
> };
>
> tem
mån 2009-09-14 klockan 11:27 +0200 skrev Guido Serassio:
> Done. Sorry for the delay, but I'm very busy (as usual ...)
>
> I have placed the preprocessed source of two failing files
> (IpIntercept.cc and QosConfig.cc) here:
>
> http://www.acmeconsulting.it/libip.zip
Odd... std::string::npos is
Hi Henrik,
>
> Can you produce a preprocessed source? That's the output of just the
> preprocessor, not actual compilarion, comparable to gcc -E option.
>
> Easier to identify what the compiler actually saw that way...
>
Done. Sorry for the delay, but I'm very busy (as usual ...)
I have placed
lör 2009-09-12 klockan 23:36 +1200 skrev Amos Jeffries:
> Updating the checklist today I again wonder if we can repeat the step
> from 2.7 and enable HTTP/1.1 on requests sent to servers
The default in 2.7 is 1.0 still. There is an option to enable 1.1, or
actually three.. (http11 cache_peer opti
Updating the checklist today I again wonder if we can repeat the step
from 2.7 and enable HTTP/1.1 on requests sent to servers
As far as I can see the missing bits 3.2 needs to take that step are:
- reject http-Upgrade requests from clients.
- reject Expect-100 requests from clients.
anythin
ons 2009-09-02 klockan 21:11 +0200 skrev Guido Serassio:
> Hi,
>
> OK, but what next ?
Can you produce a preprocessed source? That's the output of just the
preprocessor, not actual compilarion, comparable to gcc -E option.
Easier to identify what the compiler actually saw that way...
Regards
://www.acmeconsulting.it
> -Messaggio originale-
> Da: Amos Jeffries [mailto:squ...@treenet.co.nz]
> Inviato: martedì 1 settembre 2009 10.43
> A: Henrik Nordstrom
> Cc: Guido Serassio; Robert Collins; squid-dev@squid-cache.org
> Oggetto: Re: R: R: R: Squid 3 build errors on Visual Studio
Henrik Nordstrom wrote:
mån 2009-08-31 klockan 13:40 +0200 skrev Guido Serassio:
Hi,
I have found this definition:
http://msdn.microsoft.com/en-us/library/tbbk8hs6(VS.80).aspx
Hoping that helps.
Matches the standard definition from what I can tell, and should not
cause any errors...
Regard
mån 2009-08-31 klockan 13:40 +0200 skrev Guido Serassio:
> Hi,
>
> I have found this definition:
>
> http://msdn.microsoft.com/en-us/library/tbbk8hs6(VS.80).aspx
>
> Hoping that helps.
Matches the standard definition from what I can tell, and should not
cause any errors...
Regards
Henrik
squid-cache.org
> Oggetto: Re: R: R: Squid 3 build errors on Visual Studio - problem
still
> present
>
> On Sun, 2009-08-30 at 18:13 +0200, Guido Serassio wrote:
> > Hi,
> >
> > I don't know what is std::string::npos, and so I don't know what to
look
> > f
On Sun, 2009-08-30 at 18:13 +0200, Guido Serassio wrote:
> Hi,
>
> I don't know what is std::string::npos, and so I don't know what to look
> for
http://www.cplusplus.com/reference/string/string/npos/
It should be a static const, which is why I'm so surprised you're
getting an error about i
Fax. : +39.011.9781115
Email: guido.seras...@acmeconsulting.it
WWW: http://www.acmeconsulting.it
> -Messaggio originale-
> Da: Robert Collins [mailto:robe...@robertcollins.net]
> Inviato: domenica 30 agosto 2009 10.00
> A: Guido Serassio
> Cc: Amos Jeffries; squid-dev@squid-cache.org
On Sun, 2009-08-30 at 09:48 +0200, Guido Serassio wrote:
>
> c:\work\nt-3.0\src\SquidString.h(98) : error C2057: expected constant
> expression
>
> The offending code is:
>
> const static size_type npos = std::string::npos;
Can you find out what std::string::npos is defined as in your compiler'
Hi,
The patch from Amos fix the warning (not blocking problem), but the
compile problem is still present, and I don't know how to fix it.
Any file including SquidString.h doesn't build with following error:
c:\work\nt-3.0\src\SquidString.h(98) : error C2057: expected constant
expression
The off
Guido Serassio wrote:
Hi Amos,
Hi,
Who can help me to fix the following C++ errors on Visual Studio ?
1>auth_basic.cc
1>c:\work\nt-3.0\src\SquidString.h(97) : error C2057: expected
constant
expression
1>../../../src\auth/User.h(39) : warning C4099:
'AuthUserHashPointer' :
type name first
Hi Amos,
> > Hi,
> >
> > Who can help me to fix the following C++ errors on Visual Studio ?
> >
> > 1>auth_basic.cc
> > 1>c:\work\nt-3.0\src\SquidString.h(97) : error C2057: expected
constant
> expression
> > 1>../../../src\auth/User.h(39) : warning C4099:
'AuthUserHashPointer' :
> type name first
Guido Serassio wrote:
Hi,
Who can help me to fix the following C++ errors on Visual Studio ?
1>auth_basic.cc
1>c:\work\nt-3.0\src\SquidString.h(97) : error C2057: expected constant
expression
1>../../../src\auth/User.h(39) : warning C4099: 'AuthUserHashPointer' : type
name first seen using 's
Hi,
Who can help me to fix the following C++ errors on Visual Studio ?
1>auth_basic.cc
1>c:\work\nt-3.0\src\SquidString.h(97) : error C2057: expected constant
expression
1>../../../src\auth/User.h(39) : warning C4099: 'AuthUserHashPointer' : type
name first seen using 'struct' now seen using 'c
uid-cache.org
Betreff: Re: Squid-3 MacOSX IPv6 problems
Oh dear.
Can you provide the config.log generated during build and a full cache.log
from the point of startup through a failed DNS query please?
Amos
--
Please be using
Current Stable Squid 2.7.STABLE6 or 3.0.STABLE17
Current Beta Sq
rs=PAM,NCSA,LDAP,multi-domain-NTLM'
'--enable-digest-auth-helpers=password' '--enable-delay-pools'
'--enable-multicast-miss' '--enable-default-err-language=templates'
'--enable-fd-config' '--with-filedescriptors=16384' '--
Oh dear.
Can you provide the config.log generated during build and a full cache.log
from the point of startup through a failed DNS query please?
Amos
Hello again and apologies for the long delays.
If you are still interested in getting Squid-3 to build with IPv6 read on.
The current Squid-3.HEAD snapshots have been stabilized as much as I can
do for now and include a few patches which I believe get split-stack
support you need to build and
Hi Amos,
At 14.33 31/05/2009, Amos Jeffries wrote:
I've seen this occur under 2 cases. One was when a .h in the core
section failed to include config.h outside its wrapping protection. A
circular include developed and broke things.
Just found the problem: a min() & max() definition as macro i
Serassio Guido wrote:
Hi Amos,
At 11.45 31/05/2009, Amos Jeffries wrote:
>
> Someone could help me ?
>
> Regards
>
> Guido
>
They are declared in the compat/* library. Included through config.h.
compat/compat_shared.h to be exact if you need the definition (but
please only include config.h fo
Serassio Guido wrote:
Hi,
I have a little of free time, and I'm trying to build Squid 3 on MinGW,
but I'm getting the following error:
if /bin/sh ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H
-I../.. -I../../include -I../../src -I../../include
-I/usr/inclu
Hi,
I have a little of free time, and I'm trying to build Squid 3 on
MinGW, but I'm getting the following error:
if /bin/sh ../../libtool --tag=CXX --mode=compile g++
-DHAVE_CONFIG_H -I../.. -I../../include -I../../src
-I../../include -I/usr/include/libxml2 -Werror -Wall
On 05/05/2009 12:51 AM, Kinkie wrote:
> I've also planned hosting a shared windows dev system on eu, but we
> need to secure the necessary OS and devkit licenses first.
Securing somebody who will be working on that windows dev system should
come first, I guess. If nobody is going to be responsi
Hi all,
I've also planned hosting a shared windows dev system on eu, but we
need to secure the necessary OS and devkit licenses first.
On Monday, May 4, 2009, Guido Serassio wrote:
> Hi Alex,
>
> Il 02.13 04/05/2009 Alex Rousskov ha scritto:
>
> Hi Guido,
>
> Thanks a lot for the update. It
Hi Alex,
Il 02.13 04/05/2009 Alex Rousskov ha scritto:
Hi Guido,
Thanks a lot for the update. It is sad to see the results of many
years of work dissipating and I sympathize with your situation. I wonder
whether the demand for Squid on Windows is just not there OR it is the
current lack of
ironment, resources for development, source code status and a TODO
> for both Squid 2 and Squid 3.
>
>
> Build environment
>
> Squid should compile on Windows with 3 build environment, but with some
> limits:
>
> - MinGW+MSYS: full automake/autoconf/libtool/gcc support based
uid 2 and Squid 3.
Build environment
Squid should compile on Windows with 3 build environment, but with some limits:
- MinGW+MSYS: full automake/autoconf/libtool/gcc support based on GNU
toolset, but not all functionality (Large file support, IPv6,
mswin_check_ad_group helper, WSAPoll() suppo
et it
done please do so.
Though I know python well, I am not comfortable with c/c++. And as I
am a developer myself, can't really supply cash :(
I'll sit back and wait. In the meantime will try to revamp my c/c++
concepts so that I can jump in squid-devel in future.
The roadmap
Kulbir Saini wrote:
Hi list,
Is there any plans to port storeurl directives from 2.7 to 3.x? I
don't see it in 3.1 beta. One of my plugins (intelligentmirror [1])
depends on it. I am not able to release a version for squid-3.x and most
the distros are shipping squid-3.x now.
Ther
Hi list,
Is there any plans to port storeurl directives from 2.7 to 3.x? I
don't see it in 3.1 beta. One of my plugins (intelligentmirror [1])
depends on it. I am not able to release a version for squid-3.x and most
the distros are shipping squid-3.x now.
[1] http://fedora.
Don't omit the frame pointer in 64 bit mode, it makes walking the stack
for things like profiling callgraphs impossible.
Adrian
On Thu, Jun 12, 2008, Amos Jeffries wrote:
> > Just for the sake of consistency and preference for better
> > troubleshooting and testing, are there any CFLAGS that I
> Just for the sake of consistency and preference for better
> troubleshooting and testing, are there any CFLAGS that I should be using
> during configure and compile of Squid 3HEAD? I was using the same
> options I was using with 2.6, which were:
>
> CFLAGS="-DNUMTHREADS=65 -march=nocona -03 -pipe
Just for the sake of consistency and preference for better
troubleshooting and testing, are there any CFLAGS that I should be using
during configure and compile of Squid 3HEAD? I was using the same
options I was using with 2.6, which were:
CFLAGS="-DNUMTHREADS=65 -march=nocona -03 -pipe -fomit-fr
> On Tue, 2008-04-08 at 15:15 +0200, Henrik Nordstrom wrote:
>> tis 2008-04-08 klockan 17:59 +1200 skrev Amos Jeffries:
>> > Currently:
>> >fde::flags::transparent == 'intercept/non-intercept'
>> >fde::flags::tproxy == real-transparent/non-transparent
>> >(new) COMM_TRANSPARENT == real-
On Tue, Apr 08, 2008, Adrian Chadd wrote:
>
Take 3:
http://www.creative.net.au/diffs/20080408-tproxy-fix-2.diff
* restored the global flag which indicates "tproxy"ness; renamed to
enable_spoof_srv
* moved the tproxy "bind" stuff into comm.c, with a flag to comm_openex()
* changed forward.c to
tis 2008-04-08 klockan 22:17 +0800 skrev Adrian Chadd:
> > > * make sure upstream/peer-forwarded requests aren't thrown to the tproxy
> > > code.
> >
> I read the current code as "don't do that"; its the behaviour I'd like to
> maintain. We can always add the functionality later.
Yes, it is no
On Tue, 2008-04-08 at 15:15 +0200, Henrik Nordstrom wrote:
> tis 2008-04-08 klockan 17:59 +1200 skrev Amos Jeffries:
> > Currently:
> >fde::flags::transparent == 'intercept/non-intercept'
> >fde::flags::tproxy == real-transparent/non-transparent
> >(new) COMM_TRANSPARENT == real-transpa
On Tue, Apr 08, 2008, Henrik Nordstrom wrote:
>
> tis 2008-04-08 klockan 14:28 +0800 skrev Adrian Chadd:
> > Take 2: includes initial modularisation (untested; I'll test it at home
> > this weekend when I get my tproxy box back online) and configure magic
> > (with placeholders for tproxy4/freebsd
tis 2008-04-08 klockan 14:28 +0800 skrev Adrian Chadd:
> Take 2: includes initial modularisation (untested; I'll test it at home
> this weekend when I get my tproxy box back online) and configure magic
> (with placeholders for tproxy4/freebsd.)
>
> http://www.creative.net.au/diffs/20080408-tproxy
tis 2008-04-08 klockan 17:59 +1200 skrev Amos Jeffries:
> Currently:
>fde::flags::transparent == 'intercept/non-intercept'
>fde::flags::tproxy == real-transparent/non-transparent
>(new) COMM_TRANSPARENT == real-transparent
>
> Their use is currently good for what they do. A small re-na
Take 2: includes initial modularisation (untested; I'll test it at home
this weekend when I get my tproxy box back online) and configure magic
(with placeholders for tproxy4/freebsd.)
http://www.creative.net.au/diffs/20080408-tproxy-fix-2.diff
TODO:
* pull out the capabilities stuff, removing th
Adrian Chadd wrote:
On Mon, Apr 07, 2008, Amos Jeffries wrote:
We have come up with a 'final-beta' patch for squid-3 now.
http://treenet.co.nz/projects/squid/patches/tproxy-squid-3_20080407.patch
Just waiting on Laszlo final approval.
It's pretty much:
* adding a COMM_TRAN
On Mon, Apr 07, 2008, Amos Jeffries wrote:
> We have come up with a 'final-beta' patch for squid-3 now.
> http://treenet.co.nz/projects/squid/patches/tproxy-squid-3_20080407.patch
> Just waiting on Laszlo final approval.
>
> It's pretty much:
>
> * adding a
On Tue, Apr 08, 2008, Henrik Nordstrom wrote:
> tis 2008-04-08 klockan 09:57 +1200 skrev Amos Jeffries:
> > But, baby steps people:
> > - Get it in
> > - Get it tested.
> > - Polish into a class.
> >
> > So far we are at #1
>
> And I won't approve the change of sprinkling #if LINUX_TPROXY4
1 - 100 of 420 matches
Mail list logo
