NetSuite frequently rolls out code updates on Thursday nights that aren't announced or documented. The only times I have been notified or when an outstanding defect was fixed with the update, in which case I got an email. Last night a significant update was made for site builder websites ( regardless of whether they are on 2017.2 or .1). Relative URLs for CSS files are being rewritten as fully qualified absolute URLs.
If your site theme uses code like this:
<link href="/site/includes/styles.css" rel="stylesheet" type="text/css">
or this:
<link href="//www.domain.com/site/includes/styles.css" rel="stylesheet" type="text/css">
or this:
<link href="https://www.domain.com/site/includes/styles.css" rel="stylesheet" type="text/css">
Netsuite is now rewriting it on the fly to be:
<link href="http://www.domain.com/site/includes/styles.css" rel="stylesheet" type="text/css">
[FONT=arial]The only way a Site Builder site can be made HTTPS throughout and avoid the 'insecure' warning that chrome browsers will begin displaying in October:[/FONT]
http://searchengineland.com/google-emails-warnings-webmasters-chrome-will-mark-http-pages-forms-not-secure-280907
Is by using a CDN to make the shopping (i.e. non-checkout) pages secure. We need to be able to use relative links so that they can load over HTTPS through the CDN, instead of being forced to load using HTTP for whatever unknown reason this change was made. It's frustrating enough to be on a platform that never gets any updates or new features year after year, but we also get to deal with these secret updates that are unannounced, undocumented, and unexplained.
NetSuite - why aren't we allowed to control our own source code? Why have you made this change? If we wanted are links to be fully qualified, we could make it that way ourselves.