Just because you have https enabled, it doesn't mean users are going to be using it. I.e. if you have a link on your site that says:
https://my.domain.com/secretinfo.php
and the user discovers the name by following the link, they can subsequently type the following and get it via unencrypted access:
http://my.domain.com/secretinfo.php
There's nothing inherent in the presence of https capability on your webserver that would require the use of it, and though it may be possible to set the requirement on a per-directory basis, I always prefer to include it right in the file so somebody else (e.g. the webserver admin) can't make a mistake and grant plain access to it. The only downside is if the port for secure access changes, you have to edit the files.