css - ImageResizer, azure cdn, cache busting and url rewrting -

-

i planning on using imageresizer dynamically resize images. images stored on azure blobs , accessed via cdn.

at moment files paths inline , in css:

<img src="/images/someimage.jpg" />  .backgroundimage { url('/images/somebgimage.jpg')

1) recommended way redirect image paths use cdn? i've seen people use html helpers (in asp.mvc @html.cdnimage('/images/something.jpg')) doesn't work images in css.

2) there url-rewriting in web.config

given imageresizer uses querystring manipulate images, how go cache busting images after update , how point images use cdn?

client-side redirects massively increase latency, , should avoided. can't use url-rewriting between different hosts.

most css pre-processors support helper methods. if can't use helpers everywhere, manually insert cdn addresses.

cache-busting cdn-specific. changing url works everywhere (unless disable querystring-specific caching on cdn). cdns offer invalidation api. either way, open question specific cdn using isn't imageresizer question.


Comments

Post a Comment

Popular posts from this blog

java - Date formats difference between yyyy-MM-dd'T'HH:mm:ss and yyyy-MM-dd'T'HH:mm:ssXXX -

-
i trying parse date 2014-12-03t10:05:59.5646+08:00 using these 2 formats: yyyy-mm-dd't'hh:mm:ss yyyy-mm-dd't'hh:mm:ssxxx when parse using yyyy-mm-dd't'hh:mm:ss works fine, when parse yyyy-mm-dd't'hh:mm:ssxxx parseexception thrown. which correct format parse date , difference between these 2 formats? note : cannot use joda :( those valid formats: yyyy-mm-dd't'hh:mm:ss.sssz >>> e.g.: 2001-07-04t12:08:56.235-0700 yyyy-mm-dd't'hh:mm:ss.sssxxx >>> e.g.: 2001-07-04t12:08:56.235-07:00 edit: btw, "x" refer (iso 8601 time zone)
Read more

c# - Get rid of xmlns attribute when adding node to existing xml -

-
i have xml-file: <ns2:root xmlns:ns2="namespace"> <ns2:a> <ns2:b>some content</b> <ns2:c>some content</c> <ns2:d>some content</d> </a> </root> i need add new node in specific place, code is: var doc = xdocument.load(file); xnamespace ns2 = "namespace"; doc.element(ns2 + "root").element(ns2 + "a").element(ns2 + "c").addafterself( new xelement(ns2+"new", new xelement("new1", new xelement("new2","some content"), new xelement("new3", "some content")))); the output is: <ns2:root xmlns:ns2="namespace"> <ns2:a> <ns2:b>some content</b> <ns2:c>some content</c> <ns2:new> <new1 xmlns=""> <new2>some content</new2> ...
Read more