You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While upgrading to 6.38 I saw that the following line changed from extract(parse_url(urldecode($destination))); to extract(parse_url($destination));. Is there a good reason for that? Because it doesn't seem to be a backward compatible change. It breaks some of my urls such as; destination=page%253foo%253D10%2526bar%253D20.
I have created the pull request #109 in case that change make sense.
The text was updated successfully, but these errors were encountered:
The drupal_goto() function will no longer attempt to decode URLs passed to it via the "destination" query parameter in the URL. This could affect destination query parameters that were encoded using drupal_urlencode() before placing them on the page, but this should not be common since the drupal_urlencode() documentation already warned that using it in this manner could lead to unwanted double encoding.
While upgrading to 6.38 I saw that the following line changed from
extract(parse_url(urldecode($destination)));
toextract(parse_url($destination));
. Is there a good reason for that? Because it doesn't seem to be a backward compatible change. It breaks some of my urls such as;destination=page%253foo%253D10%2526bar%253D20
.I have created the pull request #109 in case that change make sense.
The text was updated successfully, but these errors were encountered: