CDN's/Reverse Proxies

  • Wonderful plugin and a great idea. ??

    It cannot work out of the box with a CDN (or Varnish server, for that matter), because the CDN or Varnish server are unaware of the device size cookie and they cannot know in a definitive way which image they should serve or cache for each device.

    This appears to be the achilles heel of the plugin. We did tinker with it a bit, and while the plugin does what it does and does it well, in the aggregate, the faster scenarios were to use a CDN/Reverse Proxy with ‘full size’ images, in spite of those images being significantly larger in most instances. In short, with no CDN in play, the plugin is advantageous; but, implementing a CDN/Proxy beats the plugin (with no CDN/proxy) by a significant margin, in spite of the image size reduction the plugin offers.

    Anyway, the point of all of this being: Do you have any plans to attempt to architect a means to overcome this? If the plugin could work alongside CDNs/Varnish/CloudFlare et.al., it would constitute a significant leap forward in mobile performance. Further, the description quoted implies a work-around for sites making use of a CDN: What would that be, exactly?

    Be well,
    AJ

    P.s. IIRC, the plugin actually did work with CloudFlare, until a ‘Cache Everything’ directive was implemented.

    https://www.ads-software.com/plugins/adaptive-images/

Viewing 2 replies - 16 through 17 (of 17 total)

  • Hi. First of all, Nevma, thank you for your efforts and please excuse my delay… could not try it on some test web until now…

    I’m using Adaptive Images 0.6.2, so far looks promising. But I have some question, could you please elaborate on the meaning of the GET parameter?

    1) I see the plugin is serving XXX?resolution=1024,1 1024 looks OK but, what is the “,1”? Pixel density?
    2) I can also see XXX?resolution=1920,1 and ?resolution=667,2 I have no “1920” entry in Adaptive settings, and 667 doesn’t seem to make sense either. And why the “,2”?

    I understand that this is for CDN only, and the image is served as needed based on device’s resolution and ignoring the extra params… Is that true or does Adaptive indeed try to serve “?resolution=667,2”?

    By the way: 1280, 1024, 640 and 360 subdirs have been created in the cache directory, as expected.

    Thanks and regards!

    Plugin Author Takis Bouyouris

    (@nevma)

    Hello, my friend,

    I am very glad that the plugin works for you!

    1) Yes, “1024” is the detected resolution of the device screen, as Javascript can report it, and “1” is the detected device pixel density.

    2) The “1920” is your screen resolution. It is not one of the breakpoints! The plugin checks your resolution and available breakpoints and it decides which is the best image size to serve.

    And yes, these parameters are for CDN usage, which, by the way, will become a lot more stable in the forthcoming 0.7.0 version? Are you paying attention @aj? ??

    Cheers,
    Takis

Viewing 2 replies - 16 through 17 (of 17 total)
  • The topic ‘CDN's/Reverse Proxies’ is closed to new replies.