Ideas - ClickDimensions Marketing Automation for D365

Submit your Product Ideas to the ClickDimensions Product Management Team below.

These will be reviewed for consideration in a future product release. It is not intended to provide Product Support. If you are having a product issue, please follow regular support procedures.


Thank you for taking the time to submit your thoughts!

Ensuring that our products address the needs of our customers is important to ClickDimensions. By providing your input, you're helping us ensure that our products are built by Marketers, for Marketers.


Information about the Product Ideas portal can be found in this support article.

To submit ideas related to ClickDimensions Intelligent Dashboards please go to this link.

Emails | Research | URL Encoding standards should be followed by ClickD & MG


The ClickDimensions email system is designed to change the included URL contrary to IETF standards and thus change the results of the included URL.

Currently ClickDimensions considers these two URLS the same:
http://www.bing.com/search?q=this+is+a+test
http://www.bing.com/search?q=this%2Bis%2Ba%2Btest
even though the resulting output of the page has a completely different meaning (different results in this case)

This "feature request" is to fix the email link encoding to fall in line with the widely adopted IETF standards and not incorrectly encode + character in URL parameters to %2B

I am submitting this as a "Feature request" as according to ClickDimensions:

"this is not considered a bug because while it may not be inline with IETF standards, it is expected functionality for our solution."

IETF standards info:

According to RFC3986 plus (+) is also a reserved character and should not be encoded - please see section 2.2 here - https://tools.ietf.org/html/rfc3986#section-2.2

Also in RFC1738 https://www.ietf.org/rfc/rfc1738.txt -
"Thus, only alphanumerics, the special characters "$-_.+!*'(),", and reserved characters used for their reserved purposes may be used unencoded within a URL." - in this situation plus is being used for its "reserved purpose" so should be used unencoded within the URL

Cheers

  • Guest
  • Jul 28 2020
  • Shipped
  • Attach files
  • +1