Bug 190523

Comment 1 Peter Wemm 2014-06-03 06:55:25 UTC

Thanks for the reminder.  This was in the first email I sent in the "RIP GNATS" thread:

"The bugzilla url requires a trailing / - everything else still redirects to 
gnats, this is intentional for a short while longer."

The scaffolding is kind of temporary and needs some help from the doc folks.  Luckily I know where to find a doc / www person :)

Comment 2 Eitan Adler 2014-06-03 06:57:35 UTC

I think he means http://bugs.freebsd.org/bugzilla/ should redirect to http://bugs.freebsd.org/bugzilla/
We should also send the strict-transport-security

Comment 3 Eitan Adler 2014-06-03 06:57:45 UTC

I think he means http://bugs.freebsd.org/bugzilla/ should redirect to http://bugs.freebsd.org/bugzilla/
We should also send the strict-transport-security header

Comment 4 Eitan Adler 2014-06-03 06:58:47 UTC

so, I still can't type.

I think he means http://bugs.freebsd.org/bugzilla/ should redirect to https://bugs.freebsd.org/bugzilla/
We should also send the strict-transport-security header

Comment 5 Bryan Drewery 2014-06-03 14:57:52 UTC

(In reply to Eitan Adler from comment #4)
> so, I still can't type.
> 
> I think he means http://bugs.freebsd.org/bugzilla/ should redirect to
> https://bugs.freebsd.org/bugzilla/
> We should also send the strict-transport-security header

+1

Comment 6 Allan Jude 2014-06-03 15:32:31 UTC

An http to https redirect, and the strict-transport header are both a good idea.

Adding the redirect for the /bugzilla without the trailing slash would also be very helpful, as that has caught me out 3 times already.

Comment 7 Bryan Drewery 2014-06-03 15:33:38 UTC

The trailing slash is in bug #190543

Comment 8 Glen Barber 2014-06-03 15:38:11 UTC

> I think he means http://bugs.freebsd.org/bugzilla/ should redirect to
> https://bugs.freebsd.org/bugzilla/

This is already the case.

Comment 9 Eitan Adler 2014-06-03 16:20:25 UTC

If so, please mark the bug 'resolved/fixed'

from a quick check it seems fixed to me.

Comment 10 Glen Barber 2014-06-03 17:15:28 UTC

(In reply to Eitan Adler from comment #9)
> If so, please mark the bug 'resolved/fixed'
> 
> from a quick check it seems fixed to me.

It was the case since the SSL cert was purchased.