On 2019-01-18, 21:48 GMT, Troy A. Griffitts wrote:
> Gitlab should now work correctly on https. Please use https and let me
> know if you have any troubles.
Thanks.
Matěj
--
https://matej.ceplovi.cz/blog/, Jabber: mc...@ceplovi.cz
GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8
Thank you TroySent from my mobile. Please forgive shortness, typos and weird autocorrects. Original Message Subject: Re: [sword-devel] gitlab httpsFrom: "Troy A. Griffitts" To: sword-devel@crosswire.orgCC:
Done.
On 1/18/19 3:09 PM, David Haslam wrote:
Done.
On 1/18/19 3:09 PM, David Haslam wrote:
> Seconded!
>
> Good observation Tuomas.
>
> btw. Chrome & Firefox both have a browser extension called HTTPS
> Everywhere.
>
> Can be useful in such situations.
>
> David
>
> Sent from ProtonMail Mobile
>
>
> On Fri, Jan 18, 2019 at 21:59, Tuomas
Seconded!
Good observation Tuomas.
btw. Chrome & Firefox both have a browser extension called HTTPS Everywhere.
Can be useful in such situations.
David
Sent from ProtonMail Mobile
On Fri, Jan 18, 2019 at 21:59, Tuomas Airaksinen
wrote:
> Hi!
>
> Still it allows http even in sign in page.
Yes - it works OK with TLS now.
Thanks, Troy.
Just tested our TLS security using Qualys. SSL Labs Server Test online.
Kept the results from being listed public.
Our current score is A
That’s very good.
What can we improve to obtain A+ ?
Best regards
David
Sent from ProtonMail Mobile
On Fri
Hi!
Still it allows http even in sign in page.
Can you configure http to forward to https, so that nobody by accident uses
http?
If using nginx, something like this:
server{
listen 80;
charset utf-8;
server_name git.crosswire.org;
location / {
return 302 https://git.cros
Gitlab should now work correctly on https. Please use https and let me
know if you have any troubles.
Troy
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change
