ons 2010-12-01 klockan 23:47 +1300 skrev Amos Jeffries:
We support said OS because that is our packaging machine.
Well. FreeBSD is FreeBSD, and autotools is not FreeBSD but FreeBSD ports
independent of FreeBSD version.
Regards
Henrik
mån 2010-11-29 klockan 18:58 +1300 skrev Amos Jeffries:
Anyone with wheel access keen to delve into auto-tools dependency hell
again?
automake-1.11.1 has been installed. Hopefully that fixes the problem.
Regards
Henrik
tis 2010-11-30 klockan 03:25 +1300 skrev Amos Jeffries:
So could you explain those condition please? It's not clear from the
code that they did anything beyond logging at the end of header parsing.
Or do you mean that by being done there they logged multiple lines per
request?
Checking..
While I do not know anybody using the obsoleted or removed features, it
may be a good idea to warn about those logging changes on squid-users
and see if there are any reasonable objections.
referer_log is a little different. Can't be fully emulated by a custom log
format. the log format
fre 2010-11-26 klockan 22:33 -0800 skrev Arthur Tumanyan:
Thanks for answer.
I have an idea.
I want add to squid support for other protos and mysql_config
support(config elements will be stored in mysql db).All data about
traffic will be stored in mysql db. An another process/software will
fre 2010-11-26 klockan 21:08 + skrev Ming Fu:
Ktrace shown that the bind failed because it try to open unix socket in
/usr/local/squid/var/run and it does not have the permission. So it is easy
to fix.
After the permission is corrected, I run into other problem, here is the log
snip:
fre 2010-11-26 klockan 11:26 -0800 skrev Arthur Tumanyan:
Hi.I havе a question about protos which supports squid.Can I add sock or VOIP
feature to squid(by adding some piece of code,for example),and if yes,how?I
mean,where to dig? I need some support.
And can squid log all incoming data in
tis 2010-11-23 klockan 03:49 + skrev Amos Jeffries:
3.2 and later send HTTP/1.1 version on all regular response lines.
CONNECT seems to have been missed somehow. This corrects the omission so
the hard-coded CONNECT reply strings send 1.1 as well.
Ouch, is that response hardcoded?
I'm
tor 2010-11-25 klockan 15:51 -0700 skrev Alex Rousskov:
Opening files for each runtime error is pretty bad from performance
point of view, although we can hope that errors do not happen often
enough to cause problems in most setups. Preloading is a better
approach, IMO, but is outside this
There was no attached patch or bugzilla reference #.
tis 2010-11-23 klockan 12:52 -0500 skrev Chad Naugle:
I submitted this to bugzilla, but it hasen't yet been it added to
trunk.
* Currently working on re-writing some core functions, (ex.
SplitString) will come in next patch.
lör 2010-11-20 klockan 18:58 +1300 skrev Amos Jeffries:
To simplify the error page loading a symlink is added from the templated
/usr/share/squid/errors/local to that /etc/squid/errors.d folder and
checked just before loading the errors/templates/ backup.
Why? I find having this symlink
lör 2010-11-20 klockan 18:58 +1300 skrev Amos Jeffries:
To simplify the error page loading a symlink is added from the templated
/usr/share/squid/errors/local to that /etc/squid/errors.d folder and
checked just before loading the errors/templates/ backup.
Why? I find having this symlink
ons 2010-11-03 klockan 17:08 +0200 skrev Tsantilas Christos:
Yes events uses the cbdataReference/cbdataReferenceDone but if we do
not lock cbdata before pass to an event the cbdata will be deleted after
the event done (when the cbdataReferenceDone called)
Only if someone calls cbdataFree
lör 2010-10-30 klockan 02:06 +0200 skrev Christian:
Hi Amos,
just packaging 3.1.9 and miss the
--with-swapdir
Your patch is scheduled for Squid-3.2.0.3 and later. I do not think it
will get merged back to 3.1 at this time with 3.2 just around the
corner. Sorry if communication have been
tor 2010-10-28 klockan 22:26 +0200 skrev Kinkie:
Well, my aim is a very modest let the damn thing build.
I do not yet understand the intricacies of cbdata, and thus I am not
able to understand when it is abused and when the abuse is benign.
There is two cbdata roles
a) Object owner, using
ons 2010-10-27 klockan 20:29 +0200 skrev Kinkie:
The build is failing on
../../src/comm.cc: In member function `void
ClientInfo::setWriteLimiter(int, double, double)':
../../src/comm.cc:2156: warning: right-hand operand of comma has no effect
That line is
tis 2010-10-12 klockan 14:51 -0300 skrev Marcus Kool:
I have various observations and questions about the Squid ICAP interface
and like to discuss these with the persons who wrote or know much about
the ICAP client part of Squid.
I like to know with whom I can discuss this and which mailing
tis 2010-10-12 klockan 17:47 +0200 skrev Kinkie:
Hi all,
this patch-let makes implements a GCC feature to hint the branch
prediction algorithms about the likely outcome of a test. This is useful
to optimize the case of singleton patterns (e.g.
CacheManager::GetInstance).
This implements
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
ons 2010-10-13 klockan 20:50 +0200 skrev Kinkie:
I agree. That's why I propose to only use it - if we do use it for
anything - for singletons, where it should be a no-brainer.
Have you checked if it makes any difference in the proposed use you see
today?
Regards
Henrik
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
mån 2010-09-27 klockan 20:24 -0300 skrev Miguel Castellanos:
I really missed it L, external redirect programs are not good for high
performance servers.
url rewrite program using the concurrent protocol performs pretty well
for high performace servers in my experience.
the old non-concurrent
mån 2010-09-20 klockan 10:26 -0600 skrev Alex Rousskov:
HTTP Compliance: do not remove ETag header from partial responses
RFC 2616 section 10.2.7 says that partial responses MUST include ETag
header, if it would have been sent in a 200 response to the same request.
Oh! Is that still in
A small bzr usage update. When committing bugfixes please use bzr
commit --fixes squid:bugnumber.
You need a little configuration to enable the squid bugtracker. In
$HOME/.bazaar/bazaar.conf add
[DEFAULT]
bugzilla_squid_url = http://bugs.squid-cache.org
You can add as many --fixes arguments as
fre 2010-09-17 klockan 12:20 -0600 skrev Alex Rousskov:
If needed, the Framework can expose the descriptor or class for writing
responses but it will become more complex and rigid if we allow such raw
access. I do not know whether it is needed. I am not a helper expert.
It's not needed. But
tis 2010-09-14 klockan 01:23 + skrev Amos Jeffries:
* Squid should be starting with EPSV not EPRT anyway. Check that your
ftp_pasv directive is set to on (default), or remove it from the config
altogether.
Shouldn't we start with PASV if it's a IPv4 connection?
There is no big need for
tor 2010-09-16 klockan 02:11 +1200 skrev Amos Jeffries:
This is the first issue with them in some months (last ones were me
buggering up the v4/v6 connection types used).
Had to ask a user to set ftp_epsv off some weeks ago due to a broken
firewall at the requested server.
And very very many
tis 2010-09-07 klockan 18:59 -0700 skrev Guy Bashkansky:
/usr/local/squid/bin/strip-query.pl
#!/usr/local/bin/perl -Tw
$| = 1; while() { chomp; s/\?\S*//; print; } ### my strip query test
If you chomp the newline then you need to add it back when printing the
result.
Regards
Henrik
fre 2010-09-03 klockan 18:03 -0700 skrev Guy Bashkansky:
Is there a way to ignore URI query terms when forming store keys?
Maybe some rule or extension?
http://wiki.squid-cache.org/Features/StoreUrlRewrite
needs to be implemented for Squid-3 as well.. currently a Squid-2 only
feature.
Regards
Looks like you are doing good progress in the right direction. Good work!
- Ursprungsmeddelande -
Dechunk incoming requests as needed and pipeline them to the server side.
The server side will eventually either chunk the request or fail. That
code is not ready yet and is not a part
ons 2010-09-01 klockan 22:54 + skrev Amos Jeffries:
If the de-chunker could be converted to not needing the entire object
before de-chunking that would allow us to avoid half the workaround and
extra options being proposed to get the other bits working.
You either dechunk or reject the
ons 2010-09-01 klockan 21:52 -0600 skrev Alex Rousskov:
An alternative is to add a fast ACL option to be able to enable HTTP/1.0
chunked responses to selected user agents (none by default).
+1 on that from me. Allows the chunked response support to evolve
experimentally until we feel
The added comment applies to the whole 6xx class, not just 601.
Note: Not entirely sure we need these as internal http status codes in
squid-3, but that's separate from this change.
sön 2010-08-29 klockan 14:57 -0600 skrev Alex Rousskov:
HTTP_INSUFFICIENT_STORAGE = 507,/** RFC2518
- Ursprungsmeddelande -
On 08/30/2010 01:44 AM, Henrik Nordström wrote:
The added comment applies to the whole 6xx class, not just 601.
We have only two 6xx constants. Are you saying HTTP_INVALID_HEADER (600)
is never sent to the client? I will adjust the comment
sön 2010-08-29 klockan 18:59 +1200 skrev Amos Jeffries:
I *think* this will remove the need for such pre-seeding.
cross-compiles should always have all run tests preconfigured for the
target, or result in a default results in probe at runtime. The tests
are there for a reason, if not we could
sön 2010-08-29 klockan 12:02 +1200 skrev Amos Jeffries:
Right now we have siblings, parents, and multicast peers with their own
types. By origin servers require both parent and origin flags to be set.
Always been the intention to have an origin type peer, just haven't got
implemented yet. But
sön 2010-08-29 klockan 11:16 -0600 skrev Alex Rousskov:
It may be confusing to have origin type peer and originserver flag at
the same time. Please consider either renaming or documenting to resolve
the naming conflict.
Should be easy to solve by documenting the option reasonably.
Regards
sön 2010-08-29 klockan 15:17 +0200 skrev kromo...@user-helfen-usern.de:
A
No need to do, I think. It's like cross compiling python. maybe, it's
possible to first create cf_gen with host compiler and set a variable
for make command, which says, which cf_gen to use. So, host cf_gen could
be
lör 2010-08-28 klockan 14:26 +1200 skrev Amos Jeffries:
The author confirmed in bugzilla that he was happy with it being labeled
GPLv2 and changed the COPYING file over before I merged.
http://bugs.squid-cache.org/show_bug.cgi?id=2905
We seem to have missed some of the GPL references in
Just noticed the external_acl/eDirectory_userip is licensed by GPLv3 or
later. This is inconsistent with the rest of the code which is GPLv2 or
later, and is also what we announce as main license for the distribution
as a whole. I see a risk here that the eDirectory_userip gets mislabeled
as
tis 2010-08-24 klockan 23:43 +1200 skrev Amos Jeffries:
Given that Squid releases have been emitting the wrong header text for
at least 4 years do you not think we should retain recognition of the
incorrect name and upgrade to the correct one?
No. We have not been sending any Trailers
mån 2010-08-23 klockan 01:17 +1200 skrev Amos Jeffries:
Updated version of Henriks patch. (why did it not get committed last
year when approved?)
Because I forgot?
* parser bug fixed to handle a list of exactly one parameter without
trailing comma (which the original would call bungled).
tis 2010-08-24 klockan 10:17 +1000 skrev Stephen Thorne:
But the situation I am experiencing is after a rejected authentication
attempt.
Squid do not consider the two cases much different.
But yes, it's generally a bad idea to keep the connection open when
trying to renegotiate NTLM, much
mån 2010-08-23 klockan 15:18 -0600 skrev Alex Rousskov:
drop_expect_100 on|off
but still send an Expect: 100-continue request. As a side effect,
it will prevent forwarding of 100 (Continue) control messages to
HTTP/1.0 clients that send Expect: 100-continue headers.
I do not
tis 2010-08-24 klockan 17:21 -0600 skrev Alex Rousskov:
Or, if Amos' rules are followed and system headers are always included
_after_ Squid ones (the problem would not even exist in this case).
Would it? Most if not all Squid headers also depends on numerous system
headers. That rule is
tis 2010-08-24 klockan 19:15 -0600 skrev Alex Rousskov:
The current header sequence (somewhere) violates the squid-then-sys rule
and causes the problem. A header sequence that follows the
squid-then-sys rule will not cause the problem. I suspect such sequence
does not exist (beyond one
mån 2010-08-23 klockan 16:42 +0200 skrev Christian:
maintaining the squid3 RPM on build.openuse.org.
3.1.4 was the last version I was able to compile without problems.
for 3.1.5 I need to apply a small patch. (squid-bootstrap.patch)
since 3.1.6 I not able to compile it for SLES10-SP3
Why are
tis 2010-08-17 klockan 17:55 +0400 skrev Valery Savchuk:
I've made some changes in src/ftp.cc for partial support of RFC-2640
(Internalization of the FTP).
This issue allows correctly see and use ftp-directories/files with
national characters, if ftp-server supports RFC-2640.
Sounds great!
sön 2010-08-22 klockan 17:18 +1200 skrev Amos Jeffries:
We should add a small compiler unit-test into configure for a while
before removing either way. No guess work then.
Do you mean a unit-test to test if the compiler warns about free()
abuses on data allocated by new?
Regards
Henrik
lör 2010-08-21 klockan 20:26 +1200 skrev Amos Jeffries:
Henrik Nordström wrote:
lör 2010-08-21 klockan 07:02 +1200 skrev Robert Collins:
it was to stop crashes with code that had been cast and was freed with
xfree(); if you don't alloc with a matching allocator, and the
platform has
lör 2010-08-21 klockan 20:07 +1200 skrev Amos Jeffries:
IMO some of them such as the malloc/calloc/free which only force a
xfoo() version internal to Squid to be hard-coded should be done with a
real symbol swap-in in the relevant header files. That way the code can
go to using
lör 2010-08-21 klockan 23:41 +0100 skrev Andrew Beverley:
I have documented all the functions and class data members. Could you
clarify whether *every* variable should be documented with doxygen
comments (including short-lived temporary ones within functions), or
just those that are part of
Why are we overloading new/delete with xmalloc/xfree?
include/SquidNew.h
this is causing random linking issues every time some piece of code
forgets to include SquidNew.h, especially when building helpers etc. And
I fail to see what benefit we get from overloading the new/delete
operators in
tor 2010-08-19 klockan 10:41 -0600 skrev Alex Rousskov:
The patch removes the ignore_expect_100 feature because we now forward
100 Continue messages. Is everybody OK with that removal?
May need to keep/resurrect it when adding next hop version check as
required by Expect..
Regards
Henrik
proper Expect processing needs to be done in our client (server side in our
terminology).
regards
Henrik
- Ursprungsmeddelande -
On 08/20/2010 06:30 AM, Henrik Nordström wrote:
tor 2010-08-19 klockan 10:41 -0600 skrev Alex Rousskov:
The patch removes the ignore_expect_100 feature
See RFC on use and meaning of HTTP version numbers.
fre 2010-08-20 klockan 08:58 -0600 skrev Alex Rousskov:
On 08/20/2010 08:36 AM, Henrik Nordström wrote:
Some aspects of http is hop-by-hop not end-to-end. Processing of Expect is
one such thing. Transfer encoding and message delimiting
lör 2010-08-21 klockan 07:02 +1200 skrev Robert Collins:
it was to stop crashes with code that had been cast and was freed with
xfree(); if you don't alloc with a matching allocator, and the
platform has a different default new - *boom*.
Allocating with new and freeing with free() is a coding
fre 2010-08-20 klockan 13:00 -0600 skrev Alex Rousskov:
On 08/20/2010 09:26 AM, Henrik Nordström wrote:
See RFC on use and meaning of HTTP version numbers.
The only relevant RFC text I can find is an informal discussion that
HTTP version is tied to a message sender, an undefined concept
Stumbled over compat/unsafe.h again when trying to compile trunk after
the purge merge.
Imho these rules in compat/unsafe.h should be dropped, replaced by
coding standards for the different sections and auditing.
- The rules originally come from lazyness in Squid-2 where we did not
want to check
# Bazaar merge directive format 2 (Bazaar 0.90)
# revision_id: hen...@henriknordstrom.net-20100820031034-\
# 0o3f9jw06pqkgmwa
# target_branch: http://www.squid-cache.org/bzr/squid3/trunk/
# testament_sha1: 7c770c668bbf0875624a280061c125890faeda6d
# timestamp: 2010-08-20 05:10:39 +0200
#
mån 2010-08-16 klockan 15:53 -0600 skrev Alex Rousskov:
Both approaches may have to deal with crazy offset management,
clientStreams manipulations, and other client-side mess.
Yes.
For now I think we need to bypass store to make this sane, and it's
probably also a step in the right direction
mån 2010-08-16 klockan 18:15 +1200 skrev Amos Jeffries:
So.. the difference being that you are suggesting the credentials
text and parsing should be done on AuthUserRequest and no AuthUser
should exist associated with it until fully authed?
AuthUser only created/looked up at the point
mån 2010-08-16 klockan 21:32 +1200 skrev Amos Jeffries:
I don't think thats making them scheme-specific as such. The child
classes inheriting from AuthUser will be doing that part.
It does. Each instance of AuthUser is scheme specific, and because of
this the related acls break down when more
mån 2010-08-16 klockan 11:43 -0600 skrev Alex Rousskov:
I am revisiting this issue in hope to enable HTTP/1.1 to clients. If
Squid properly dechunks requests on the client side, what should happen
to that dechunked request on the server side? Let's start with the most
general case were we
mån 2010-08-16 klockan 13:30 -0600 skrev Alex Rousskov:
Since Squid is a program and not a human being, we do need to hard-code
a single default. Clearly, there will be ACLs to change the behavior,
but if no options apply, we still need to do something.
Yu have more-or-less said no to
mån 2010-08-16 klockan 14:08 -0600 skrev Alex Rousskov:
Should we try implement what you described then? In summary:
- If the next hop is known to be 1.1, send a chunked request.
- Otherwise, try to accumulate the full body, with a timeout.
Send 411 if we timed out while
sön 2010-08-15 klockan 19:01 +0100 skrev Markus Moeller:
Not sure if it is under revision control, but I get it with rsync. I have
removed it from the patch
If you can then it's better to access the sources using bzr.
http://wiki.squid-cache.org/Squid3VCS
Regards
Henrik
While trying to investigate Bug 2936 it seems the auth refcounting state
in trunk is somewhat borked.
The state of ntlm auth is considerably worse in trunk than 3.1.
- Fails if external acls is used (any, not just with grace=.. as in 3.1)
- Fails with refcount error on second NTLM handshake.
sön 2010-08-15 klockan 23:26 + skrev Amos Jeffries:
- Fails if external acls is used (any, not just with grace=.. as in 3.1)
any ideas why?
No, haven't really dug into the code yet. Was just observing to verify
that the claims in 2936 could be reproduced and found a much worse
situation
mån 2010-08-16 klockan 01:43 + skrev Amos Jeffries:
Basic flow around that absorb is:
create empty AuthUser local_auth_user
Gah.. I think it should be
* Perform auth. Uses and results in an AuthState (scheme specific) or if
you prefer AuthRequest but matches badly with both ntlm digest.
fre 2010-08-13 klockan 18:54 -0500 skrev Mark Nottingham:
P.S., if any other squid-dev people are on github, we can add you to the
group, FWIW, although like I said, this is read-only...
I have a github account. hno as mostly everywhere else. But I see you
already noticed that.
Regards
I don't get how any of these changes can be relevant to the bug in
question.
Regards
Henrik
fre 2010-08-13 klockan 19:42 -0600 skrev Alex Rousskov:
On 08/12/2010 03:37 AM, Amos Jeffries wrote:
revno: 10728
committer: Amos
fre 2010-08-13 klockan 19:42 -0600 skrev Alex Rousskov:
You may want to test the attached fix instead. I do not know whether it
helps with Bug 2936 specifically, but it does fix a bug that smells
related to those issues because Bug 2936 test script uses HTTP/1.0 messages.
Looks right to me,
lör 2010-08-14 klockan 10:31 -0600 skrev Alex Rousskov:
This move makes it clear that the logic applies only to the message
being examined and not some irrelevant information such as HTTP version
supported by Squid.
How do chunking fit into this?
Is the Transfer-Encoding property of the
lör 2010-08-14 klockan 07:07 -0600 skrev Alex Rousskov:
On 08/14/2010 02:58 AM, Henrik Nordström wrote:
fre 2010-08-13 klockan 19:42 -0600 skrev Alex Rousskov:
You may want to test the attached fix instead. I do not know whether it
helps with Bug 2936 specifically, but it does fix a bug
lör 2010-08-14 klockan 12:26 -0600 skrev Alex Rousskov:
The patch does not change the time when the message headers are
examined. Moreover, the [unchanged] persistency checking code does not
look at Transfer-Encoding at all. Did I completely misunderstood your
concern?
Just confusion.
lör 2010-08-14 klockan 21:10 +0100 skrev Markus Moeller:
Hi,
Please find attached a patch to add Proxy- and WWW-Authenticate.
Regards
Markus
Looks fine, but need to be wrapped up in kerberos ifdefs, same as used
for the main code kerberos client.
Regards
Henrik
sön 2010-08-01 klockan 16:33 +1200 skrev Amos Jeffries:
+// if IPv6 is split-stack, prefer IPv4
+if (Ip::EnableIpv6IPV6_SPECIAL_SPLITSTACK) {
+// NP: This is not a great choice of default,
+// but with the current Internet being IPv4-majority has a higher
success
Looks like the new src/stub_debug.cc file have not been tested?
Seems to be missing a whole lot #include files. It's not pulling in
squid.h so it needs to include every header it needs.
The errors I get are:
stub_debug.cc: In function 'void _db_print(const char*, ...)':
Applied.
tor 2010-07-08 klockan 12:35 +0300 skrev Milen Pankov:
Hi,
Recently I needed to use squid_db_auth against mysql database with md5
encrypted passwords.
I read a recent discussion on this list (Joomla DB authentication
support hits Squid!:)) that was regarding integration with
ons 2010-07-14 klockan 00:53 + skrev Amos Jeffries:
Thats the plan. Those three objects I said we have to work with are the
parameters available to internalStart().
My copy only have two parameters..
internalStart(HttpRequest * request, StoreEntry * entry)
So far I have the else case of
tis 2010-06-29 klockan 16:58 +0800 skrev Weibin Yao:
I noticed the
guideline(http://wiki.squid-cache.org/Squid2CodingGuidelines) is that:
Code MUST be formatted with GNU indent version 1.9.1 and these exact
options indent -br -ce -i4 -ci4 -l80 -nlp -npcs -npsl -d0 -sc -di0 -psl
How could I
mån 2010-06-28 klockan 00:05 + skrev Amos Jeffries:
Do you want to go through and remove or should I?
I'll do it and submit it as a merge.
Regards
Henrik
sön 2010-06-27 klockan 17:19 +1200 skrev Amos Jeffries:
At present it means enable/disable IPv6 support in IP::Address, with a
corollary of also disabling stuff that requires that storage support.
ipv6 address storage is not an issue imho. First of all I very much
doubt we have any target
lör 2010-06-26 klockan 17:27 +1200 skrev Amos Jeffries:
Part of the problem at present with snapshots is the 3-way labeling of
trunk/3.HEAD/HEAD. snapshot is expecting to find tarballs at:
.../Versions/v3/3.HEAD/squid-3.HEAD.tar.bz2
What are you others thoughts about finally removing the
I'd like to see most uses of the USE_IPV6 conditional removed, limiting
it to just the parts dealing with IPv6 networking.
Having conditionals sprinkled out over the code is bad, and even badder
if the conditional isn't really needed. The basic IPv6 functionality
like being able to parse IPv6
sön 2010-06-27 klockan 02:42 +1200 skrev Amos Jeffries:
Nah, more on that later. I still have hope on getting the work flow I
desire wrt trunk. Current have some rather stupid limitations.
Okay. Can we start discussion on that now. So that it gets cleared up
before 3.2.0.1 starts
lör 2010-06-26 klockan 14:16 -0600 skrev Alex Rousskov:
I do not have any strong opinions or preferences but packaging trunk
code using some numbered version is a little confusing, IMO, especially
when you need to work with something that was packaged a while ago: Was
that snapshot produced
lör 2010-06-26 klockan 14:22 -0600 skrev Alex Rousskov:
In other words, define USE_IPV6 as use IPv6 addresses in system calls?
Correct.
And currently it is defined as handle IPv6 addresses in URLs and use
IPv6 addresses in system calls?
Yes. Without USE_IPV6 we fails to even parse anything
lör 2010-06-26 klockan 14:24 -0600 skrev Alex Rousskov:
That is better. Although, in the ideal world, it is Squid2 that should
be more specific and we could just use trunk for Squid3, Squid4, etc.
Don't think there will be a Squid-4 any time soon, but who knows.
For me Squid-2 is not a
ons 2010-06-23 klockan 07:36 -0500 skrev Sandeep Kuttal:
I am looking for changing the Squid code little bit to cache POST
messages.
caching POST messages in Squid is hard to implement due to Squid not
buffering the POST body before forwarding the request.
Regards
Henrik
ons 2010-06-23 klockan 12:19 +0200 skrev Guido Serassio:
Squid on Windows should work in transparent mode when the packet redirection
is done from an external device like a firewall.
2.7 may be a little picky about that, insisting on being able to get the
original destination ip.
A
mån 2010-06-21 klockan 21:52 +0100 skrev Andrew Beverley:
I have done some initial scoping, but have discovered that in order to
mark a packet using setsockopt(), the process needs to be run as root.
Are you sure it needs root and not just a suitable capability flag? From
what I can tel
tis 2010-06-22 klockan 12:26 +0100 skrev Andrew Beverley:
So, is the best way of implementing this to do the same as transparent
proxying, and check whether the (proposed) marking option is enabled in
squid.conf when executing restoreCapabilities?
Either that, or we always request to keep
sön 2010-06-20 klockan 19:03 + skrev winet...@gmail.com:
No wonder even with port mapping and redirection working, the transparent
proxy still not working. Where can I get or request one that compiled with
transparent proxy feature?
squid-dev is the best place to discuss this.
How does
ons 2010-06-16 klockan 00:36 +0200 skrev Kinkie:
What's your guys opinion about this article?
It deals with some specific algorithms Varnish uses to increase
performance to account for the fact that it's running under a
real-world VM.
Yes.. quite expected result actually. Similar benefits can
ons 2010-06-16 klockan 10:09 +0200 skrev Kinkie:
Actually the thing I found the most interesting is that it suggests to
use page-aware object placements so that big structures traversal is
easier on the VM.
The optimization he discusses is mainly to make the operation more
optimal in precense
tis 2010-06-15 klockan 01:11 + skrev Amos Jeffries:
To use the TPROXY available in 2.6.3x kernels you require Squid-3.1 and
iptables 1.4
There is also a TPROXY4 patch for Squid-2 from Visolve. Not sure which
versions is applies to but Squid-2.7 something.
Regards
Henrik
tis 2010-06-15 klockan 20:26 +1200 skrev Robert Collins:
Bug 2950: HTTP responses with no Date, Last-modified or expired can
now be cached (given an appropriate refresh_pattern). Previously we
were not caching them in case of an infinite loop in cache farms:
however Squid adds Date:
lör 2010-06-12 klockan 22:53 +1200 skrev Amos Jeffries:
Henrik informs that loosp using fd_set() (select and win32-select) must
be kept below FD_SETSIZE or they can hang Squid or cause out-of-bounds
memory errors.
NP: Squid-2 does not appear to limit select() like this. May need
301 - 400 of 597 matches
Mail list logo
