Still seeing 301 with yourls 1.8.1

[saraedum]

In my yourls setup this does not seem to work.

I installed your plugin and activated it. There are no other active plugins.

However, I still get a 301 in the browser developer tools being returned for the redirect. I disabled caching in the browser, so I don't think it's a problem with the browser.

How can I debug why this does not seem to work for me?

cc @Dominik-rueth

[Dominik-rueth]

Actually, it used to work until quite recently. There was a link whose content I changed every week, and I was always forwarded to the new address. Now, I am sent to the address from last week in my Firefox browser on Ubuntu. I do not have the same problem in my Chromium browser as I did not use the link there before.

…

On 04.12.21 21:38, Julian Rüth wrote: In my yourls setup this does not seem to work. I installed your plugin and activated it. There are no other active plugins. However, I still get a 301 in the browser developer tools being returned for the redirect. I disabled caching in the browser, so I don't think it's a problem with the browser. How can I debug why this does not seem to work for me? cc @Dominik-rueth <https://github.com/Dominik-rueth> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASZSBKPN7D7XOKJSWGUNRD3UPJ33ZANCNFSM5JL6IBGQ>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[saraedum]

I am not sure what your Chromium is doing. But yourls is definitely sending a 301 here. The browser is allowed to cache that information and it does. Firefox might have more aggressive caching than Chromium which explains why the problem is browser specific. But the underlying issue is that this plugin has no effect in our setup.

[Dominik-rueth]

I expressed myself unclearly. I think Chromium was working all right because I rarely use it and therefore did not use it recently with that link.

…

On 05.12.21 09:18, Julian Rüth wrote: I am not sure what your Chromium is doing. But yourls is definitely sending a 301 here. The browser is allowed to cache that information and it does. Firefox might have more aggressive caching than Chromium which explains why the problem is browser specific. But the underlying issue is that this plugin has no effect in our setup.