Callback URLs truncated when containing an ampersand

oauth

#1

Hello there!

While building a Social Login plugin, I’ve noticed that Twitter does not seem to accept a URL with an ampersand in it for the app’s callback / return URL.

I understand that this field isn’t required for the app to function; however, it seems pretty odd to completely truncate a valid URL in this field. Here’s an example:

  1. Before saving: http://cloud.skyver.ge/3i461z2S3P2w
  2. After saving: http://cloud.skyver.ge/1p0M181M0t2Q

The integration with Twitter login still functions, but if this field won’t accept a valid URL for the callback, it seems unnecessary to have it in the first place.

Is this a known bug / something that will be patched in the future so that more than one parameter can be accepted for the URL?

Thanks!


#2

I can confirm this still appears to be occurring.