# Google Maps Onebox data is not cached

**URL:** <https://meta.discourse.org/t/google-maps-onebox-data-is-not-cached/59124>\
**Category:** Feature\
**Created:** [March 15, 2017, 1:39am UTC](https://meta.discourse.org/t/google-maps-onebox-data-is-not-cached/59124 "2017-03-15T01:39:01Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![glebm](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/glebm/32/120891_2.png) [@glebm](https://meta.discourse.org/u/glebm)\
**Post date:** [March 16, 2017, 1:15am UTC](https://meta.discourse.org/t/google-maps-onebox-data-is-not-cached/59124/8 "2017-03-16T01:15:05Z")

</div>

@mpalmer Good point, I haven’t realized the intent is to respect the cache headers.

However, the onebox currently does not respect the headers. Instead, it always caches everything forever.

> <https://github.com/discourse/onebox/blob/main/lib/onebox/engine.rb#L65>

It only does the correct thing for Google Maps currently by accident. If Google Maps changes the cache headers tomorrow, it will no longer do the correct thing.

---

_[View the full topic](https://meta.discourse.org/t/google-maps-onebox-data-is-not-cached/59124)._