Running into a particularly menacing issue on one of our client's live servers. They have 2 facing servers in the farm (client facing), running as a balanced farm. We deploy our changes to FACING-01 and have replication to FACING-02 to replicate all the SharePoint specific changes, not web.config ans such.
Problem is, we're deploying changes to CSS files through SharePoint Designer onto FACING-01 which resolves their address http://www.clientweb.co.za, but when browsing the site on the given URL the changes do not pull through.
I've added a script to the root to show the name of the server we're browsing (http://www.clientweb.co.za/server.asp) to make sure that we're on FACING-01 which always seem to be the case, but browsing the CSS files pulls through a previous version.
We assessed output cache enabled in SharePoint and disabled it, did an IIS reset but still nothing. I tried appending ?ver=1 to the style links on our master page to force a refresh but still nothing. All code changes appear as expected, it's just Style Sheets.
Should we connect to http://www.clientweb.co.za/ through SharePoint Designer instead of using the server name (FACING-01)? Might this make a difference?
Thank you for all the pointers guys, you helped me in the right direction. In the end, it turned out to be an XSL file used to style a CQWP that was causing, what appeared to be caching, in regards to the CSS. Someone in the development team CTRL-C + CTRL-V the CSS link tags meant for the Master page, into the XSL as they where both open in SP-D. An honest mistake.