These redirects SHOULD be cached:

These redirects should NOT be cached:

These are the results gathered from the Redirect Caching Tests. Each test name contains three pieces of information:

• status code - 301, 302, 303, and 307
• cache headers - future (Expires and max-age 1 month in the future), none (no Expires nor max-age headers), past (max-age=0 and Expires 1 month in the past)
• cookies - none (no Cookie request header)), const (the Cookie header is the same for all redirect requests), vary (the Cookie header varies for all redirect requests)

The results are broken into two tables:

• table 1 - redirects that should be cached
• table 2 - redirects that should not be cached

This grouping is based on RFC 2616 and feedback from the Httpbis working group. Note that "success" varies: in table 1 success means the redirect was cached; in table 2 it means the redirect was not cached. The browser's behavior is shown ("cached" or "not") and drawn in green if the behavior matches the specification. Note that all redirects have a "Cache-Control: private" response header. This should not affect caching, but some browsers incorrectly don't cache when this header is present.