We use a cache buster variable to force the loading of new CSS. The respond-proxy.html file has a faulty regex that expects .css to be the last part of the string.
E.g., the stylesheet:
Will attempt to load cross domain, using:
Notice the double question marks.
We had a similar issue with compressed assets. Our are .css.gz, sometimes. For now we just hacked the code in the HTML, but maybe there's a cleaner solution?
Resolves Issue #59: Cross domain CSS files with ? in URL won't load