[ckan-dev] CKAN 2.8.2 HTTP to HTTPS

Thu May 16 01:03:10 UTC 2019

Hello Judy,

Depending on how you have CKAN setup, for the most part it does not care at
all if it's being served over HTTP or HTTPS. That job falls on your
front-end server, such as nginx, Apache, ELB, etc...

Rather than ckan, you should look for the documentation of whatever you're
using to serve ckan to the world. You may also need to double check the
links you use in your customized templates, such as to images, are using //
or HTTPS:// (but if it was done right in the first place it shouldn't be an
issue)

Thank you,
Tyler Kennedy

On Wed., May 15, 2019, 20:51 Judith Moran, <Judith.Moran at nt.gov.au> wrote:

> Hi,
>
>
>
> Can someone advise what they did to move from HTTP to HTTPS.
>
>
>
> The links I have found are fairly old  i.e. 2016 hoping someone can
> provide info for 2.8.2.
>
>
>
>
>
> Regards,
>
>
>
>
>
>
>
> *Judy Moran*
> *Manager Data Strategy*
> Department of *Corporate and Information Services*
> Northern Territory Government of Australia
>
> *T:*  892 96550
> *E:*  DataStrategy.NTG at nt.gov.au
>
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20190515/c4df9764/attachment-0002.html>