Redirect caching loop & busting

[bwbroersma]

When I go to /site/nevertested.example/results
I get an 302 to /site/nevertested.example/ with an cache-control: max-age=60 and expires: now + 60 seconds.
When the probes then finish within 60 seconds .. the site will goto /results, which is cached, so it will reload he status page, which will redirect again .. until the 60 second cache is expired.

Also, the request to /site/probes/domainname/?_=jstimestamp is interesting, since the jstimestamp is done for cache busting principles, while the probe returns the same cache-control: max-age=60 and expires: now + 60 seconds.
Which all in all feels a bit unclean to me.