Author Topic: Static vs Dynamic content  (Read 5513 times)

Kristopher

  • Newbie
  • *
  • Posts: 3
  • Karma: +0/-0
Static vs Dynamic content
« on: January 11, 2012, 03:58:18 AM »
I installed a new TED 5000 this weekend.  It's an awesome kit. 

I'm setting up a reverse proxy on an Apache webserver for the TED gateway in my house.  (using ProxyPass)  I am experimenting with a cache on this reverse proxy to take some network pressure off of the gateway.  This makes the Footprints pages load really fast compared to hitting the gateway directly.

Can anybody comment on what content should never be cached?  It seems to be working well if I don't cache anything under /api or /history.  I also excluded a file named com.ted.footprints.Footprints.nocache.js simply because of it's name.  :)

Right now I'm using this in Apache.

Code: [Select]
CacheEnable disk /
CacheDisable /com.ted.footprints.Footprints.nocache.js
CacheDisable /api
CacheDisable /history

TedDev

  • TED Software Developent
  • Administrator
  • Full Member
  • *****
  • Posts: 158
  • Karma: +0/-0
Re: Static vs Dynamic content
« Reply #1 on: January 12, 2012, 02:17:08 AM »
Any of the html, htm, js, and image files can all be cached. Those only change w/ firmware updates.

The .cgi, .xml, .csv, and .raw files should not be cached. However, those are limited to the /api and /history directories so it sounds like you have it pretty close.

Kristopher

  • Newbie
  • *
  • Posts: 3
  • Karma: +0/-0
Re: Static vs Dynamic content
« Reply #2 on: January 12, 2012, 10:03:21 AM »
Thanks.  That's just the information I needed!

By the way, I noticed that there's a reference to /images/wximages/twclogo.jpg somewhere in the code.  This file doesn't exist on the device.

Gateway Version 1.0.483
Daughterboard Version 1.0.94
Footprints Version 1.0.262
MTU Version 1.0.61