of operating system (-versions ?)
What does not doing it's job mean here? Sending corrupt or incomplete
data?
One, the other or even Both, depending on your kernel.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer
In message [EMAIL PROTECTED], =?ISO-8859-1?Q?Andreas_R
=F8sdal?= writes:
On Sun, 13 May 2007, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], =?ISO-8859-1?Q?Andreas_R
=F8sdal?= writes:
Hello,
I have a question about a recent change done in SVN trunk:
http://varnish.projects.linpro.no
, it appears.
Varnish doesn't care about '?', but if you have cookies it will
not cache.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained
In message [EMAIL PROTECTED], sure
ndar p writes:
Hi,
When i compile the code,i got this error
Expected positive indentation.
what is the actual error it is?
file and line information, please ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since
-engineer (I find the
capitalization strategy particularly confusing).
The starting point is FreeBSD's style(9) manual page, and yes, the
capitalization is not consistent.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer
.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
varnish-dev
In message [EMAIL PROTECTED], Mark Nottingha
m writes:
On 2007/11/21, at 4:54 AM, Poul-Henning Kamp wrote:
The only truly precise way to characterize varnish, IMO, is A
webserver that uses HTTP to get at its content.
This is a good characterisation. It would probably be more correct to
say
and built a storage_umem
allocator facility that rides on Solaris' excellent libumem (highly
scalable allocator) which we also ported to run on Linux and FreeBSD
(and Mac OS X): https://labs.omniti.com/trac/portableumem
Next steps?
Can you mail me a link to the patch ?
--
Poul-Henning Kamp
Is this FAQ fodder ?
In message [EMAIL PROTECTED], =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=
writes:
Poul-Henning Kamp [EMAIL PROTECTED] writes:
You could try the following in vcl_recv:
if (req.http.accept-encoding) {
set req.http.accept-encoding =3D regsub
i'm wondering how varnish determines how much memory it should
consume...
It uses all memory it can for caching.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute
that compiled code only calls VRT_*
functions, you need to keep a VRT_re_test() wrapper around for that
reason.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can
.
Downloading: yes, we buffer.
Uploading: no, we don't.
Does varnish support x-sendfile type responses?
Not at present, but it sounds like it could be useful, I'll add it
to the post-2.0 ideas list.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since
; on a system where the hot
cache entries can be stored on disk, it would seem that the swap-based
method would be superior.
Well, it's slightly more complex than that, we mmap with the
MAP_NOSYNC flag so it should be about a wash.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED
~ deflate) {
set req.hash +=3D deflate;
}
}
where do I find that in Varnish itself?
See cache_center.c::cnt_lookup() [search for VCL_hash_method(sp);],
and cache_hash.c::HSH_Copy(), HSH_Compare() and HSH_Lookup().
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED
?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
varnish-dev mailing
In message [EMAIL PROTECTED], Artur Bergman
writes:
On Jun 23, 2008, at 1:26 AM, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED],
Artur Bergman
writes:
I have written an multicast HTCP purger, essentially a perl script
that listens to HTCP purges and then purges from the local
In message [EMAIL PROTECTED], Olivier Beau writes:
- Which version of varnish is good for production ?
Hi Olivier,
We are getting very close to a 2.0 release, so right now the best code
we have is the trunk version from subversion.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
-dev
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
varnish-dev
, and basically we decided that perfect
statistics were not as important as fast speed.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained
?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
varnish-dev mailing
my questions about .so and sendfile ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
. It knows better [...]
Ok, fair enough.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
I have committed the EINTR patch and, I hope, fixed the two testcases,
please check this and send me your latest solaris patch.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never
present in
the backend connection, and added one of it's own using the IP
address of the backend server as the content of that header.
6) The incorrect document was fetched for the backend because the
Host header was not correct.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
done.
http://varnish.projects.linpro.no/wiki/VCLExampleLongerCaching
section *How it should work*
set obj.ttl = 1w;
maybe changed to
set obj.ttl = 7d;
or in function static double TimeUnit(struct tokenlist *tl) add w Id
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL
;
set obj.ttl = 2h;
...
set obj.ttl = 1d;
...
set obj.ttl = 1w;
set obj.ttl = 4w;
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute
the backend times them out.
How you TCP connections get out of sync between varnish host and backend
host I have no idea...
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute
and saw
a request (please tell us which!) after more ESI features, but I'm not
sure how to voice my preference.
Get a wiki login[1], edit the page.
[1] They are free and we happily give them away, but you have to ask
so we kan keep spammers away.
--
Poul-Henning Kamp | UNIX since Zilog
://projects.linpro.no/mailman/listinfo/varnish-dev
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
it:
18446744073709551615 - 2^64 = -1
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
: vcc_acl.c
FAIL: ./tests/v00017.vtc
Can you try to run that test by hand with a -v flag ?
cd .../bin/varnishtest
./varnishtest -v tests/v00017.vtc
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since
In message 4a305b14.7080...@caringo.com, Mike Melson writes:
Is there anyway to catch follow a 301 redirect from a backend server
to a host that has NOT been defined as a backend in varnish?
No.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since
convenient for the code.
I'll change it.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
/varnistest/tests/e6.vtc for an example.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
time to fetch,
has no cacheability, but does not get marked pass in vcl_fetch ?
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately
have no better ideas.
Grace mode helps a lot, if you can use it.
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained
we would make the
non-support for -b explicit, until the code could be written.
There are no objections to supporting it, it's just code to be
written by somebody... (nudge, nudge, wink, wink...)
Poul-Henning
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP
= IP(req.http.x-forwarded-for);
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence
is needed.
Do you have an opinion regarding the suggestion for the VCL compile time case?
There should not be two different syntaxes, the above should be used in
both cases.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer
39 matches
Mail list logo
