In message
, Jean-Baptiste Quenot writes:
>1) is it a difficult task to provide a meaningful error message in the
>crash report?
It's a bug which only got fixed just after 3.0.1 unfortunately.
>2) why not issue a 413 entity too large when some headers longer than
>http_req_hdr_len, instead of c
Dumb questions:
1) is it a difficult task to provide a meaningful error message in the
crash report?
2) why not issue a 413 entity too large when some headers longer than
http_req_hdr_len, instead of crashing?
I mean is it normal behavior for varnish to crash in those
circumstances, or is it a bu
In message
, Jean-Baptiste Quenot writes:
>With 3.0.1 rc1 I get the following crashes frequently:
>
>https://gist.github.com/1188467
>
>Is it related to HTTP/1.0? I can't see a crash with HTTP/1.1.
It is probably related to cookies longer than the http_req_hdr_len param
--
Poul-Henning Kamp
Hello Varnish,
With 3.0.1 rc1 I get the following crashes frequently:
https://gist.github.com/1188467
Is it related to HTTP/1.0? I can't see a crash with HTTP/1.1.
Any idea?
--
Jean-Baptiste Quenot
___
varnish-dev mailing list
varnish-dev@varnish-c
gw1 varnishd[11313]: Child (9244) Panic message:
> Assert error in WSLR(), shmlog.c line 236:
> Condition(w->wlp < w->wle) not true.
> thread = (cache-worker)
> ident = Linux,2.6.35-28-server,x86_64,-sfile,-hcritbit,epoll
> Backtrace:
> 0x4235f8: /usr/sbin/varnishd() [0
Hi there,
Since upgrading from Varnish 2.0.6 to Varnish 2.1.3 (both with the
Apache LogFormat patch applied) I get this error in production:
Apr 15 11:54:31 gw1 varnishd[11313]: Child (9244) Panic message:
Assert error in WSLR(), shmlog.c line 236:
Condition(w->wlp < w->wle) not tru