That pertains to a minority of use-cases anyway. Futhermore, I have observed, that some users that employ a CMS which supports the canonical tag (like e.g. Wordpress) actually override the default value in their Ajaxify call:
Currently, the default value is:
canonical: true
I am wondering, whether it would not be safer to set the default value to:
canonical: false
...instead.
That would get rid of problems like the one described here.
EDIT: Default value changed to
falsefrom version 7.3.3The following applies to the situation before version 7.3.3
Here's why the canonical parameter was introduced in the first place - mainly in order to cater for correct URLs in the event of redirects...
That pertains to a minority of use-cases anyway. Futhermore, I have observed, that some users that employ a CMS which supports the
canonicaltag (like e.g. Wordpress) actually override the default value in their Ajaxify call:Currently, the default value is:
I am wondering, whether it would not be safer to set the default value to:
...instead.
That would get rid of problems like the one described here.
What do you think?