GitHub camo caches the redirection

[hiendv]

github/markup#224 (comment)
github/markup#224 (comment)

[hiendv]

Well, it didn't go away.
atmos/camo#85
lemurheavy/coveralls-public#414
So instead of revalidating the original 302 request, they revalidate the final URL.

[hiendv]

I didn't, again. I thought it's because of Cloudflare but it is not.

curl -I "https://hireable.0x1115.org/hiendv"

HTTP/1.1 301 Moved Permanently
ETag: "bcabf2d2f9492a6e38d7425f919b1ba8"
Cache-Control: no-cache, no-store, must-revalidate
Location: /hireable-error.svg
Content-Type: text/html; charset=utf-8
Content-Length: 69
Date: Fri, 19 Aug 2016 10:12:06 GMT
Connection: keep-alive

What about the final URL?

curl -I "https://hireable.0x1115.org/hireable-error.svg"

HTTP/1.1 200 OK
Last-Modified: Wed, 17 Aug 2016 19:33:06 GMT
Content-Length: 741
Cache-Control: max-age=0
Content-Type: image/svg+xml
Date: Fri, 19 Aug 2016 10:14:28 GMT
Connection: keep-alive

Let see whether atmos has an answer or not.

[hiendv]

Well, it may not camo's fault. I deployed https://github.com/atmos/camo and they did not cache
https://ihatecamo.herokuapp.com/4b216b8d0ce71f76aca9d112234e12ef7f4e6b8e?url=https://hireable.0x1115.org/hiendv

[hiendv]

Investigating.
Dispite the fact that GET parameters don't affect the result at all. I changed my job profile between each time of previewing

[![](https://hireable.0x1115.org/hiendv?foo=bar)](https://hireable.0x1115.org/p/hiendv)
[![](https://hireable.0x1115.org/hiendv?fooo=bar)](https://hireable.0x1115.org/p/hiendv)

[hiendv]

Updated.

curl -I "https://hireable.0x1115.org/hireable-error.svg"

HTTP/1.1 200 OK
Cache-Control: no-cache
Content-Length: 741
Content-Type: image/svg+xml
Date: Fri, 19 Aug 2016 11:44:51 GMT
Last-Modified: Wed, 17 Aug 2016 19:33:06 GMT
Server: Caddy