G
goo
Guest
Yes, I woke up with the same thought right now .. that is of course the problem. That’s why I can’t get the second parameter as well... thanks!! Sendt fra min iPad 21. aug. 2018 kl. 22:45 skrev Matt Baker : Update from Progress Community Matt Baker There are several characters in URLs that are considered "unsafe". The list includes ' " / \ ? & ; # = + (and maybe a more ). These are all delimiter characters and have special meaning. Having them appear in a value of a field is going to cause problems. Some of these are dependent on where in the URL they appear. In your case the padding character for a base64 encoded value is treated as a delimiter in the query string. So any URL processing is going to chop this apart at the equals sign. The sender needs to URL encode the value properly in order for it to make it through properly. View online You received this notification because you subscribed to the forum. To unsubscribe from only this thread, go here . Flag this post as spam/abuse.
Continue reading...
Continue reading...