From owner-freebsd-bugs@freebsd.org Fri Jan 22 02:29:33 2016 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 278E3A8B9E9 for ; Fri, 22 Jan 2016 02:29:33 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from mail.strugglingcoder.info (strugglingcoder.info [65.19.130.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.strugglingcoder.info", Issuer "mail.strugglingcoder.info" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 18C711F4E; Fri, 22 Jan 2016 02:29:32 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from localhost (unknown [10.1.1.3]) (Authenticated sender: hiren@strugglingcoder.info) by mail.strugglingcoder.info (Postfix) with ESMTPA id 0F4F8D361D; Thu, 21 Jan 2016 18:29:32 -0800 (PST) Date: Thu, 21 Jan 2016 18:29:32 -0800 From: hiren panchasara To: Phil Eaton , koobs@FreeBSD.org Cc: freebsd-bugs@freebsd.org Subject: Re: 502 accessing bugzilla Message-ID: <20160122022932.GK33895@strugglingcoder.info> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="cN0A5YokcrYPGsSB" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jan 2016 02:29:33 -0000 --cN0A5YokcrYPGsSB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable + koobs from bugzilla admin team. On 01/20/16 at 06:00P, Phil Eaton wrote: > I am trying to access the FreeBSD bugzilla browse section here > . > But I keep getting a 502 on Chrome on FreeBSD. Firefox appears to be fine > and the page returns as expected. Is this the right list to report this? >=20 > Thanks! Koobs, can you please look into this? OR forward to appropriate person/list? Thanks, Hiren --cN0A5YokcrYPGsSB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAABCgBmBQJWoZQMXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNEUyMEZBMUQ4Nzg4RjNGMTdFNjZGMDI4 QjkyNTBFMTU2M0VERkU1AAoJEIuSUOFWPt/lLtsH/An1oCl+oXzhp+aqPXsnT0Dx cgdLAtf43nvouhpxp60HnXTbf2xMoaKdj0GZ80z3xeCQq43luinPbC5JhkCpX0kr LtArHjp/NA7HRkBbf0m3B7ywGredftAcAWfhX/EQAwF83ijVulTbk4lzzVPbwIAe lrz3zzor+gehDUBBvs7yLTBaxdm45kTAQ7v6rFdK516pkPRZEObo3wvDm2gEbnaF wLlsPCrIEouWSe06fPhpd3L9k46LRpi4fyLRAoDwqJzQeQoxdpiz4/Swy8cy3dYI VVLxUuvVIHM72F9GJqOAVxPpUKaJhzqHB7GryXHxGWGaQsw8n7n9WgQb848K5PU= =mfWd -----END PGP SIGNATURE----- --cN0A5YokcrYPGsSB--