Changes between Initial Version and Version 1 of Ticket #27201, comment 10


Ignore:
Timestamp:
Nov 2, 2016, 12:27:52 PM (8 years ago)
Author:
Andrew Badr

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #27201, comment 10

    initial v1  
    33> How would you suggest we generate a manifest of you static assets without parsing your CSS files?
    44
    5 We're getting a bit off-topic, but the current implementation would work even if it didn't parse or alter the contents of any CSS files. To use this ticket as an example, the font file without a hash in its filename ("CrimsonText-Bold.ttf") would load just fine. Of course, this makes setting caching headers a little more complicated, but then again, Django can't guarantee, for example, that you aren't dynamically loading some static assets with JavaScript. Those paths in JS would not get converted in the current manifest system.  What we have now is an incomplete and (to me, a little) surprising solution. There's a case to be made that the path rewriting should make it easier to distinguish altered paths from original ones in order to address this caching issue.
     5The current implementation would work even if it didn't parse or alter the contents of any CSS files. To use this ticket as an example, the font file without a hash in its filename ("CrimsonText-Bold.ttf") would load just fine. Of course, this makes setting caching headers a little more complicated, but then again, Django can't guarantee, for example, that you aren't dynamically loading some static assets with JavaScript. Those paths in JS would not get converted in the current manifest system.  What we have now is an incomplete and (to me, a little) surprising solution. There's a case to be made that the path rewriting should make it easier to distinguish altered paths from original ones in order to address this caching issue.
Back to Top