On Thu, Feb 14, 2008 at 11:16 AM, Poul-Henning Kamp [EMAIL PROTECTED] wrote:
In message [EMAIL PROTECTED], Erik writes:
- web server: Centos 4 + Apache 2.0.52 + PHP 4.3.9 + Varnish=
1.1.2
Ok, I think this bug has been fixed, as also indicated by ticket 188
Hi,
I can confirm it's fixed
On Thu, Feb 14, 2008 at 12:02 PM, Dag-Erling Smørgrav [EMAIL PROTECTED] wrote:
You didn't say which version you're using, but from this backend
definition, it's certainly not trunk. It would be very helpful to
know whether you see the same behaviour with trunk.
Hi,
I tried trunk and I
Marco Molinari [EMAIL PROTECTED] writes:
Dag-Erling Smørgrav [EMAIL PROTECTED] writes:
If the point of this is to allow the client to Shift-Reload, you
should purge the URL to force a reload from the backend, instead of
piping the request.
That's the point, I just needed a quick way to
Hi,
I have seen the same behaviour on my Apache2 server with php5 installed.
Many users got blank pages
when navigating around the website. I couldn't figure out what the
problem was so I simply removed varnish
and the problem disappeared.
Another problem I had was that php's X-FORWARDED-FOR
I can now reproduce it and I found a lot of info.
I wrote a simple script that keeps on reloading itself, adding some
chars each time; I disabled compression both in Apache and in PHP and
I connect my browser through a 2.6 Squid proxy; and now I can't see
PHP pages larger than 8000 bytes. I also
Pretty much all my pages are in the 10k to 30k range, so I guess I am
confirming this. It sucks that this is so hard to reproduce :(
I'm considering moving all the stuff I want cached to a different
hostname / ip address, and let the clients talk directly to Apache again
for the pages
On Feb 6, 2008 2:57 AM, Arne Kepp [EMAIL PROTECTED] wrote:
(Maybe this should be on -misc ?)
Ok, moved.
Thank you for your reply. I'm using PHP and I had it gzip'ing, then I
tried to use mod_deflate, but they're reporting the problem anyway.
But I think the problem is similar. In fact, thanks