MapGuide RFC 75 - Adding caching support to GETTILEIMAGE ¶
This page contains an change request (RFC) for the MapGuide Open Source project. More MapGuide RFCs can be found on the RFCs page.
Status ¶
RFC Template Version | (1.0) |
Submission Date | () |
Last Modified | (Zac Spitzer) Timestamp |
Author | (Zac Spitzer) |
RFC Status | (proposed) |
Implementation Status | () |
Proposed Milestone | (2.2) |
Assigned PSC guide(s) | (when determined) |
Voting History | (vote date) |
no vote |
Overview ¶
Currently the tile service has no support for http cache semantics.
Motivation ¶
HTTP caching is a very simple way of increasing performance.
Proxy servers cannot currently cache MapGuide GETTILEIMAGE responses, without custom configuration and overrides
Proposed Solution ¶
Adding cache headers to tile service.
This would require support adding the source tile timestamp to the HTTP header and then support returning 304's as required
Implications ¶
None
Test Plan ¶
TBD
Funding/Resources ¶
TBD
Trac Tickets ¶
Add proper cache headers & file date to GETTILEIMAGE response