#27201: Django 1.10 with STATICFILES_STORAGE breaks on absolute path in CSS with
double slash
--------------------------------------+------------------------------------
     Reporter:  andrewbadr            |                    Owner:  nobody
         Type:  Cleanup/optimization  |                   Status:  new
    Component:  contrib.staticfiles   |                  Version:  1.10
     Severity:  Normal                |               Resolution:
     Keywords:                        |             Triage Stage:  Accepted
    Has patch:  0                     |      Needs documentation:  0
  Needs tests:  0                     |  Patch needs improvement:  0
Easy pickings:  0                     |                    UI/UX:  0
--------------------------------------+------------------------------------

Comment (by andrewbadr):

 Replying to [comment:9 charettes]:
 >
 > How would you suggest we generate a manifest of you static assets
 without parsing your CSS files?

 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.

--
Ticket URL: <https://code.djangoproject.com/ticket/27201#comment:10>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.e7f1bb0b3d5bf9fa2bbc69cd374ed926%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to