I recently installed the BuyNow module of v 5.0 into a page then applied SSL to the page.  The page is giving a mixed content warning.  Further investigation reveals that the page is trying to call module.css from the site root and the page is not found.  The IIS's 404.htm is not a secure page so the warning is triggered.  Should BuyNow's module.css be refered to in the page?  When I remove the BuyNow module from the page, the page renders https: with no warnings, so this doesn't seem to be caused by something else.