Hi Bruce/Folks,
Here's the situation.
I've got all internal links (images, css, scripts) in my site pointing to fully qualified urls, rather than relative.
I did this because I have a lot of redirect logic going on, and found that if I didn't do this the urls were the original url + the relative path.
There might be a better way around this problem, sure. If there is, Bruce, be gentle.However, there comes a problem with this.
Depending on whether or not you use "www" or the root non-www url to get to the site, the css url('<relative path>') calls mean that images/icons won't show.
To get a visual on this, visit 1)
http://sandersnoonan.com.au - working great!, then visit 2)
http://www.sandersnoonan.com.au - the little icons (css url('') relative folders) aren't showing.
[Edit: You'll want to visit those urls in separate incognito browser tabs, as if you visit them one after the other the icons work okay]
So the relative paths in the css will have
http://www.sandersnoonan.com.au added on, and I'm guessing? that this stops things from working?
Really not sure what's happening here, but am guessing it'll be a simple enough solve.
This stack is interesting (
http://stackoverflow.com/questions/940451/using-relative-url-in-css-file-what-location-is-it-relative-to). The W3 rules are that the relative url in a stylesheet is relative to the documents folder. So why does "www" / non-www make a difference?
Cheers.