Hello @superpoincare
The reason this happens is that page enhanced rules work with and without trailing slash. We don’t know if the user wants the trailing slash or not. Also, we can’t add a rewrite rule in the Nginx or Apache config because we don’t know which URLs should be the opposite. For example, the contact form 7 plugin doesn’t work with a trailing slash, but we don’t know if the user installed that plugin. Also, we don’t know what plugins work with what rules and we don’t want to have to add a million possibilities for each plugin there is.
We are considering to add some options in the settings in the future for this.
Thank you!
Thread Starter
Ramanan
(@superpoincare)
Hi Marko,
But in my observation, it happens due to the option for xml.
Can I choose it to be off?
Hello @superpoincare
Yes, of course, you can. It was added as an option but it does slow down the cache engine.
We redirect URLs without trailing slash using PHP because we don’t know if the URL you’re visiting should be redirected or not (we could break some rewrite rules if we did).
You could add his own rewrite rules to force a trailing slash. This depends of course which engine you are using (Apache or Nginx).
Thank you.
Thread Starter
Ramanan
(@superpoincare)
Hi Marko,
I’ve noticed that switching off “Handle XML mime type” although correctly changes the config file and htaccess, the checkmark in the settings *page* stays on.
This was also noticed here:
https://wordpress.org/support/topic/handle-xml-mime-type/
Also how would the redirect to trailing slash look like in Apache?
There might be exceptions which I might not be aware of.
