Re: Ticket #250 (POST error when using Opera)
In message [EMAIL PROTECTED], Nick Loman writes: Hi there Just to update you on my experience with Varnish 1.1.2, [...] At this point we _really_ urge everybody to upgrade to Varnish 2.0. The release candidate 1 was released this week, and we are ready to cut the release now. Poul-Henning PS: for those who can attend, there is a release party in Oslo on 2008-10-21, email [EMAIL PROTECTED] for details. -- 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-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: Ticket #250 (POST error when using Opera)
Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Nick Loman writes: Hi there Just to update you on my experience with Varnish 1.1.2, [...] At this point we _really_ urge everybody to upgrade to Varnish 2.0. The release candidate 1 was released this week, and we are ready to cut the release now. Hi Poul-Henning, I started on Varnish 2.0-rc1, which was 99% great, but we experienced a problem which was unfortunately a show-stopper. See my post on the 9th October, Mac connection problem with Varnish 2.0-rc1. If it wasn't for that, I'd be using Varnish 2.0 on our production sites right now. Regards, Nick. ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: Ticket #250 (POST error when using Opera)
In message [EMAIL PROTECTED], Nick Loman writes: I started on Varnish 2.0-rc1, which was 99% great, but we experienced a problem which was unfortunately a show-stopper. See my post on the 9th October, Mac connection problem with Varnish 2.0-rc1. If it wasn't for that, I'd be using Varnish 2.0 on our production sites right now. I looked at that and didn't see anything in the varnishlog output that indicated a problem. I have no idea what the safari error you quoted in the message mean... -- 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-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: Ticket #250 (POST error when using Opera)
Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Nick Loman writes: I started on Varnish 2.0-rc1, which was 99% great, but we experienced a problem which was unfortunately a show-stopper. See my post on the 9th October, Mac connection problem with Varnish 2.0-rc1. If it wasn't for that, I'd be using Varnish 2.0 on our production sites right now. I looked at that and didn't see anything in the varnishlog output that indicated a problem. Nor did I! ;) I have no idea what the safari error you quoted in the message mean... No, nor do I. But it meant that a user couldn't use the site properly, and when I downgraded to Varnish 1.1.2 it worked absolutely fine. This was Varnish 2.0-rc1 with totally default settings, so I couldn't blame a dodgy VCL. Where should I go from here? I could try the latest trunk, I guess? Regards, Nick. ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: Ticket #250 (POST error when using Opera)
In message [EMAIL PROTECTED], Nick Loman writes: Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Nick Loman writes: I started on Varnish 2.0-rc1, which was 99% great, but we experienced a problem which was unfortunately a show-stopper. See my post on the 9th October, Mac connection problem with Varnish 2.0-rc1. If it wasn't for that, I'd be using Varnish 2.0 on our production sites right now. I looked at that and didn't see anything in the varnishlog output that indicated a problem. Nor did I! ;) Are you sure that transaction was from one of the failing views ? Where should I go from here? I could try the latest trunk, I guess? Make sure you get a failing transaction in the varnishlog. If that shows nothing abnormal, try getting a tcpdump of that transaction and see if there is anything abnormal in that. -- 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-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
