It's also really interesting testing out how search engines deal with a 307 redirect, as these tend to be more on the client side (from everything I've seen - e.g. when Chrome requests something that's cached in the browser) rather than done at the server level. This might actually be the first instance where I've seen it done at the server level. In many ways it works very much like a regular temporary redirect, but it has some other slighly different characteristics around how it handles GET, POST and PUT methods. This is one that'll make for a potentially quite interesting 307propellertest and I'd be really keen to know how frequently URLs - both before and after - are crawled by search bots.
Like the other tests, I've gone with two fairly beefy paragraphs - the first kind of explaining what this is, to an extent, and the second as just being filler. Just adding a bit of meat to this otherwise bland and empty HTML bones. I'm losing the will to live writing this, but it'll probably be worth it in the end - provided we get some exciting or unexpected data out of the search engines when we see how they either crawl or index this content.