Primary tabs

Comments by User

Friday, April 28, 2017 - 09:47

Nice work, our lovely platform is now more secure! :)


Keep on being awesome ^^

Friday, April 28, 2017 - 09:32

hey, thank you for your creation. For my project I added more layers.

Tuesday, March 21, 2017 - 06:53

Yes, there is an easy solution.

Just change the login form.


<form action="/node?destination=node" method="post" id="user-login-form" accept-charset="UTF-8" class="compact-form">



<form action="" method="post" id="user-login-form" accept-charset="UTF-8" class="compact-form">


But before changing this line, all other bugs should be fixed^^


Monday, March 20, 2017 - 20:40

@capbros yes! With http the browser connects to the server on port 80 and with https it connects on the port 443. Connecting on port 443 adds a transport security layer 


As I can see, the certificat is now up to date. But with a quick view I found two todo's:


1. With https the previews of all art's are broken:

how it is now:

How it should be:



The login is not with forced https.

Currently the login credentials are sent with http and the user never sees https, if he starts with http. In addition to this if he manually goes to https and is logged in at http, he will not be logged in at https.


Thursday, March 16, 2017 - 10:21

Yes, it is true! The complete loginprocess is handled via http, and afterwards no secure connection is used, ever! Therfore you see no warning, because no SSL-Cert is ever loaded to secure the connection... Just look at the current url you are on!


Visit for secure connection...