# 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:** 7

<div class="post-metadata">

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

</div>

I’m with @codinghorror: this isn’t a bug.

Consider the difference in response headers from the two requests:

```
$ wget -O /dev/null -S https://xkcd.com/123 |& grep Cache-Control
  Cache-Control: max-age=300
  Cache-Control: max-age=300
$ wget -O /dev/null -S https://goo.gl/maps/R6nj3Qwf2LR2 |& grep Cache-Control
  Cache-Control: no-cache, no-store, max-age=0, must-revalidate
  Cache-Control: private
  Cache-Control: no-cache, must-revalidate

```

(There are multiple headers because of redirects being followed)

It would be a bug if the onebox library cached data when the origin said not to. The other way around… not so much.

---

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