why i get response if it is a post request with pass?
geoff at uplex.de
Mon Dec 28 11:17:20 CET 2015
-----BEGIN PGP SIGNED MESSAGE-----
On 12/28/15 10:25 AM, יעקב ירמולובסקי wrote:
> I'm using varnish 3 so I don't think that I have
Right, but your VCL is evidently doing something in the form of error
handling, since it reacted to the fetch error (which is seen in VCL as
response code 503) by redirecting, with response code 302 and a
Location header. The redirect goes to "/oops" with obj_status=503,
obj_response=Service Unavailable and the request XID in the query
string, which sounds like custom error handling.
> As for the backend, I'm using Apache 2.2.31 and I have checked the
> logs but it seems that everything goes well there and I get status
Sure, your Apache might be getting 200, but it took over 5 seconds to
do so, and Varnish didn't wait that long. Look here:
ReqEnd c 2005611725 1451213252.184271336 1451213257.219164610
0.000056505 5.034824371 0.000068903
The second-to-last number tells you that Varnish waited just over 5
seconds for the response and gave up, causing:
FetchError c http first read error: -1 0 (Success)
That's a first byte timeout, which is very likely set to 5 seconds.
Always look for FetchError records in cases like this. "http first
read error" is very common, it means your backend was too slow.
> Maybe I need to enable something in the Apache config?
Impossible to say from a distance. It might help to tune your Apache,
but it might be something else entirely, such as database fetches in
your application that are taking too long.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
-----END PGP SIGNATURE-----
More information about the varnish-misc