Date: Thu, 21 Jan 2016 18:29:32 -0800 From: hiren panchasara <hiren@strugglingcoder.info> To: Phil Eaton <philneaton95@gmail.com>, koobs@FreeBSD.org Cc: freebsd-bugs@freebsd.org Subject: Re: 502 accessing bugzilla Message-ID: <20160122022932.GK33895@strugglingcoder.info> In-Reply-To: <CAByiw%2BryCFJcQR8iMZ-PfbD5XB%2BgnKkn3knYA6FgPD-4qFwPKw@mail.gmail.com> References: <CAByiw%2BryCFJcQR8iMZ-PfbD5XB%2BgnKkn3knYA6FgPD-4qFwPKw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--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 > <https://bugs.freebsd.org/bugzilla/buglist.cgi?product=3DPorts%20%26%20Pa= ckages&component=3DIndividual%20Port(s)&resolution=3D--->. > 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160122022932.GK33895>