From owner-freebsd-apache@FreeBSD.ORG Tue Jul 29 02:18:16 2008 Return-Path: Delivered-To: apache@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 837C01065671 for ; Tue, 29 Jul 2008 02:18:16 +0000 (UTC) (envelope-from dwiest@vailsys.com) Received: from dprobd02.vailsys.com (dprobd02.vailsys.com [63.149.73.146]) by mx1.freebsd.org (Postfix) with ESMTP id 64A468FC16 for ; Tue, 29 Jul 2008 02:18:16 +0000 (UTC) (envelope-from dwiest@vailsys.com) Received: from dpfuser01.vail (dpfuser01.vail [192.168.129.103]) by dprobd02.vailsys.com (Postfix) with ESMTP id 51C548A5CDE for ; Mon, 28 Jul 2008 21:00:13 -0500 (CDT) Received: from dfwdamian.vail (dfwdamian.vail [192.168.129.233]) by dpfuser01.vail (Postfix) with ESMTP id 396235C5A for ; Mon, 28 Jul 2008 21:00:13 -0500 (CDT) Received: (from dwiest@localhost) by dfwdamian.vail (8.13.8/8.13.8/Submit) id m6T20C8J056837 for apache@freebsd.org; Mon, 28 Jul 2008 21:00:12 -0500 (CDT) (envelope-from dwiest@vailsys.com) X-Authentication-Warning: dfwdamian.vail: dwiest set sender to dwiest@vailsys.com using -f Date: Mon, 28 Jul 2008 21:00:12 -0500 From: Damian Wiest To: apache@freebsd.org Message-ID: <20080729020012.GA56803@dfwdamian.vail> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: FireFox error -12229 w/ apache+ssl-1.3.41.1.59 X-BeenThere: freebsd-apache@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Support of apache-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jul 2008 02:18:16 -0000 I've been tearing my hair out over a problem with the apache+ssl-1.3.41.1.59 port running under FreeBSD 7.0-release and am hoping that someone can provide some suggestions. We have a Perl CGI based web application that was using apache+ssl-1.3.27.1.48_2 on FreeBSD 4.8. When we upgraded to the latest version, we began getting strange errors from a few web browsers; specifically the latest release of Safari and FireFox 2.0. FireFox 2.0 will return error code -12229 when the client performs POST requests; GET requests work fine. FireFox 3.0 does not return this error, nor does IE 6 or 7. The latest version of Safari just generates an error about being "unable to establish a secure connection". I do not see any errors recorded in Apache's log file; the POST request shows a status code of 200. >From what I can tell this is most likely a browser error. I'm wondering if someone's seen this problem before? I also don't understand why the latest release of the apache13-ssl port causes this error to occur when a much older release did not. I suppose asking people to upgrade to FireFox 3 is an option, but I don't have a solution for Safari users. I'd really appreciate any help with this matter. If it would help, I can send my httpsd.conf file along with some packet dumps if you'd like. Thanks! -Damian