That fixed it, thanks.
I'm curious about how that goes bad, though. The element read:
" />
Was the header block being saved in the cache with an https site_url() and then served up?
I have the standard FUEL .htaccess file.
It seems that the reason relative links are interpreted as HTTPS links is because the page header defines a BASE element with https in the URI.
'assets_absolute_path' is set to false.
I will note that I do not have this problem on my staging server, just on production. The FUEL files are the same in the two environments. So, I suspect it is really a problem with FUEL interacting with the P…