Removing the redirect from the server doesn't necessarily remove a copy already cached by a browser. There's no reliable way to make every visitor discard that cached response immediately.
First, check the original URL with a client that has no cached redirect, such as a fresh browser profile or a command-line request. That helps distinguish a browser cache problem from a redirect still being served by the application or another layer.
For your own browser, clearing cached data can help. For visitors, a different path on the main site avoids relying on the old URL, though it means changing the address you want to use.
!quietly+miswired_6:
So even if the server is fixed, some browsers may keep following the old redirect until their cached copy goes away?
Lenn:
Yes. How long that lasts can depend on the browser and the cached response, so don't assume everyone will update at the same time.