Timeline for Can I reuse a URL after it's used for a 301 redirect?
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 7, 2018 at 22:18 | history | edited | Maximillian Laumeister♦ | CC BY-SA 4.0 |
added 8 characters in body
|
| Nov 7, 2018 at 22:13 | history | edited | Maximillian Laumeister♦ | CC BY-SA 4.0 |
added 8 characters in body
|
| Nov 7, 2018 at 22:07 | history | edited | Maximillian Laumeister♦ | CC BY-SA 4.0 |
added 8 characters in body
|
| Nov 7, 2018 at 21:56 | comment | added | Maximillian Laumeister♦ | @ceejayoz Not true, at least this discussion leads me to believe that it is not. Browsers are smart enough not to get caught in a redirect loop caused by a cached redirect. | |
| Nov 7, 2018 at 21:55 | history | edited | Maximillian Laumeister♦ | CC BY-SA 4.0 |
added 270 characters in body
|
| Nov 7, 2018 at 16:54 | comment | added | ceejayoz | @J_F_B_M There's no requirement for such a mechanism in the spec, to my knowledge. As such, I wouldn't rely on specific browser implementations of a cache clear. 301s are supposed to be permanent, and should be treated as such. | |
| Nov 7, 2018 at 16:53 | comment | added | JFBM | @cee Is there no mechanism that tries to detect whether maybe the local cache is stale? | |
| Nov 7, 2018 at 16:50 | comment | added | ceejayoz | Some browsers cache 301s forever, so your advice will potentially result in an infinite redirect loop in some cases. | |
| Nov 7, 2018 at 3:52 | comment | added | Scramble | thank you for the explanation. it's very useful information. | |
| Nov 7, 2018 at 3:44 | history | edited | Maximillian Laumeister♦ | CC BY-SA 4.0 |
deleted 6 characters in body
|
| Nov 7, 2018 at 3:37 | history | answered | Maximillian Laumeister♦ | CC BY-SA 4.0 |