Redirect error

WordPress 7.0 PHP 8.3.20 Broken Link Checker 2.4.8 Server local Reproduce the problem See image 1 . Click on ‘Recheck’ in the first row of the table. See image 2 . Log: see image 3 . The redirect disappears from the screen but still exists. This topic was modified 2 weeks, 1 day ago by almendron . Hello @almendron I tried to replicate the issue, but no matter how many times I tried, I was unable to make the redirection information disappear from the table, even after rechecking the links. When you reloaded the page, the issue persisted? Which plugin are you using for the redirections? If so, I suggest you to make a backup of your site, and run a Conflict Test by deactivating any other plugin and using a default theme. Maybe another component is causing this. Kind regards, Jair. I’ll run the tests you mentioned. I don’t use any redirect plugins. However, I don’t think there will be any issues because everything worked fine with versions of WordPress prior to version 7. Hi @almendron , I’ll run the tests you mentioned. I don’t use any redirect plugins. Since we couldn’t replicate the issue, it’s tough to say what exactly might have caused it. Please do let us know how the above test goes. Is the issue only with one specific URL? Or do you notice the same with more URLs like this? If you still encounter an issue after the conflict test, then please share the URL shown in the results so we can get a better idea. Regards, Nithin Tests: plugins disabled and one of the default WordPress themes selected. Result: the error persists. It affects all redirects. I think the problem is that I’m running the tests on a local server. The next test will be to update one of my websites on the production server Hi @almendron The redirect tis actually correct result curl -IL https://www.abc.es/informacion/JUICIO11M/index.asp HTTP/2 301 request-id: 1780127053-2254-f49a02fe-d572-4418-aa2b-e44ec69b0e73 content-type: text/html; charset=iso-8859-1 accept-ranges: bytes cache-control: max-age=900 date: Sat, 30 May 2026 07:44:13 GMT x-cache: MISS, MISS, MISS vary: Accept-Encoding, User-Agent location: https://www.abc.es/informacion/JUICIO11M/ strict-transport-security: max-age=31557600; includeSubDomains alt-svc: h3=":443";ma=86400,h3-29=":443";ma=86400,h3-27=":443";ma=86400 HTTP/2 200 request-id: 1780126943-1361-b4a39d2a-03c5-414e-91fd-1ace9339d238 content-type: text/html; charset=iso-8859-15 accept-ranges: bytes age: 110 date: Sat, 30 May 2026 07:44:13 GMT x-cache: MISS, MISS, HIT vary: Accept-Encoding, User-Agent set-cookie: geo={"c": "AU","r": "WA","o": "OC"}; max-age=86400; path=/ cache-control: max-age=0, no-cache, no-store strict-transport-security: max-age=31557600; includeSubDomains alt-svc: h3=":443";ma=86400,h3-29=":443";ma=86400,h3-27=":443";ma=86400 content-length: 70076 I tried to replicate the re-check on a local server but it worked well and kept the redirect report. I believe the main concern would be fixing the post / page to include the proper final URL. Best Regards Patrick Freitas I’ll check it again. Hi @almendron I tested again and still can see a redirect happening for that URL. You can use a website like this to test, as you can see in all locations the result showing a 301 redirect: https://check-host.net/check-http?host=https://www.abc.es/informacion/JUICIO11M/index.asp&csrf_token=0ece452f3fa092c6d9e678e1c57c5d2166b1e4a7 Best Regards Amin Hello @almendron , I hope the above suggestions helped addressing the issue. We didn’t hear from you for a while, so I’ll be marking this thread as resolved. Please feel free to reopen it, and reply, if you need any further assistance. Best Regards, Dmytro