admin管理员组

文章数量:1122832

Permanent 301 redirections are stored in client browser cache. Theoretically this means they cannot be modified after they has been set, because browser will just follow the initial, cached redirection, and won't even make a new request and ask a server if there has been redirection updates.

However, although they are 301 permanent, posts permalinks can be modified, and seems like browser is not saving them in cache.

Is this because of the Cache-Control: no-cache, must-revalidate, max-age=0, no-store header, which I see in Dev Tools -> Network tab?

My main questions are:

  • Are post permalinks cached/not cached by default?
  • Is wp_redirect() cached/not cached by default?
  • I am actually using vip_substr_redirect. Is it cached by default?
  • If I change the post permalink or update the wp_redirect or vip_substr_redirect settings, can I be sure that clients will be properly redirected?
  • If I delete a post with custom permalink, and use that exact same permalink in another, new post, can I be sure clients won't get 401?

本文标签： redirectAre post permalinks and wpredirect() redirections saved in browser cache

版权声明：本文标题：redirect - Are post permalinks and wp_redirect() redirections saved in browser cache? 内容由网友自发贡献，该文观点仅代表作者本人， 转载请联系作者并注明出处：http://www.betaflare.com/web/1736300748a1930930.html， 本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容，一经查实，本站将立刻删除。