[ECODP-dev] https issue

Mon Jun 24 08:35:55 UTC 2013

Hi Bert,

1. No new files should be required (but you will need a SSL cert, we just
self-signed one for the test server).

We have configured NGINX to use SSL on port 443 (standard) using our certs,
and have configured all calls to /user/* on port 80 to redirect to the SSL
server. The Apache config should not need to be changed. You will also need
to make sure that you are using the most recent version of our wsgi.py file
(which makes sure that the correct scheme gets passed to CKAN so it can
redirect properly).

2. Are you using the most recent wsgi.py file?

Regards,
John

On 23 June 2013 22:51, Bert Van Nuffelen <bert.van.nuffelen at tenforce.com>wrote:

> Hi,
>
> 2 items here:
>
> *) Can you provide some additional inside in the new setup? Also if
> new files are required please inform us.
>
> *) On our internal test if a user logs in  then he is redirected to
> http://192.168.33.176/data/en/user/dashboard?__no_cache__=True&id=api
>  which is under http and not under https.
>
>   That seems contradictonary.
>
> Bert
>
> --
> Bert Van Nuffelen
>
> Semantic Technologies Software Architect at TenForce
> www.tenforce.be
>
> Bert.Van.Nuffelen at tenforce.com
> Office: +32 (0)16 31 48 60
> Mobile:+32 479 06 24 26
> skype: bert.van.nuffelen
>
> _______________________________________________
> Ecodp-dev mailing list
> Ecodp-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ecodp-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.okfn.org/mailman/private/ecodp-dev/attachments/20130624/4caadef3/attachment.html>