Fixes issue 169. (https added to file url)

It turned out that when a user was not logged in, the problem with displaying files with names containing wierd characters didn't exist. The only problem was that a logged-in user tried to display a non-secured page. 
(don't know why it only occured with files with wierd characters in their names, though; with "normal" files https is added automatically)