The ccadb.org site is now https.
Please let me know if you run into any problems with the ccadb.org site.
Thanks for your patience.
Kathleen
___
dev-security-policy mailing list
dev-security-policy@lists.mozilla.org
On 2/9/18 7:52 AM, Kathleen Wilson wrote:
On 2/7/18 11:41 AM, Kathleen Wilson wrote:
All,
At 6pm PST on Thursday, February 8th, we will begin the migration of
ccadb.org to https.
It is possible that during this migration users may receive errors
when trying to access the ccadb.org site.
On 2/7/18 11:41 AM, Kathleen Wilson wrote:
All,
At 6pm PST on Thursday, February 8th, we will begin the migration of
ccadb.org to https.
It is possible that during this migration users may receive errors when
trying to access the ccadb.org site.
All,
Something went wrong, so the changes
On 1/30/18 6:19 AM, Gervase Markham wrote:
On 30/01/18 00:48, James Burton wrote:
I was doing research on the ccadb.org site and was surprised to find that
the site is running only in HTTP and is not using HTTPS. Now, I understand
that GitHub pages don't support HTTPS for custom domains but you
On 30/01/18 00:48, James Burton wrote:
> I was doing research on the ccadb.org site and was surprised to find that
> the site is running only in HTTP and is not using HTTPS. Now, I understand
> that GitHub pages don't support HTTPS for custom domains but you could
> always use CloudFlare for HTTPS
Hrm, I didn’t realize it had been restricted. The gist is that bug is closed as
incomplete as of three months ago and there is a new bug that I don’t have
access to: https://bugzilla.mozilla.org/show_bug.cgi?id=1409786
> On Jan 29, 2018, at 20:02, James Burton wrote:
>
> Hi
Hi Jonathan,
I haven't got the required permission to access bug 1376996.
Thank you,
James
On Tue, Jan 30, 2018 at 12:57 AM, Jonathan Rudenberg
wrote:
>
> > On Jan 29, 2018, at 19:48, James Burton via dev-security-policy <
> dev-security-policy@lists.mozilla.org>
> On Jan 29, 2018, at 19:48, James Burton via dev-security-policy
> wrote:
>
> I was doing research on the ccadb.org site and was surprised to find that
> the site is running only in HTTP and is not using HTTPS.
There is already a bug about this:
8 matches
Mail list logo