Incompatible with trailing slash rewriterule (Apache)

[rgbkgb]

Hello, Thanks for your awesome work ! However, the magic link URL is not working properly because we have an apache rewriterule adding a trailing slash, then it leads to a 404. Do you have any idea about how we could mitigate this issue ? Maybe we could change the source code in order to add a trailing slash to your magic link URL ? Thanks in advance for your help !

Arthur

[rgbkgb]

We've added a RewriteCond to our .htaccess in order to not add a trailing slash to the magicUrl, however we are using CloudFlare, and it redirects us to the homepage. We have made extensive testing and this behaviour is related to CloudFlare :/ Since the endpoint could change, it's hard to create a bypass cache rule on CloudFlare side, any ideas ?

[elindydotcom]

@rgbkgb - do you know if this is still an issue with Cloudflare? Was looking at this project as an option to meet a need but Cloudflare is a must. So was just wondering if this is still an issue for you or if you found a workaround inside cloudflare.

[jcatello]

Wanted to bump this, forcing the trailing slash is sometimes necessary because of caching, so it would be good if the URL will work with a trailing slash as well

[aaemnnosttv]

Thanks @jcatello – is the trailing slash applied as a redirect on the web server in that case or filtered into the URL WP generates?

[jcatello]

Its a redirect applied by the webserver, typically for WP Rocket users:

https://docs.wp-rocket.me/article/131-redirection-to-enforce-trailing-slash-on-urls#trailing-slashes-on-nginx-servers

[jcatello]

https://github.com/aaemnnosttv/wp-cli-login-command/pull/58 Do you want to review this?

[aaemnnosttv]

Planning on addressing this soon. Working on updating CI infra first before merging other changes.