{"id":6129,"date":"2020-06-26T16:01:16","date_gmt":"2020-06-26T14:01:16","guid":{"rendered":"https:\/\/test11988.futurehost.pl\/?p=6129"},"modified":"2020-10-20T14:06:06","modified_gmt":"2020-10-20T12:06:06","slug":"decoding-percent-encoded-octets-in-urls","status":"publish","type":"post","link":"https:\/\/test11988.futurehost.pl\/decoding-percent-encoded-octets-in-urls","title":{"rendered":"Decoding Percent Encoded Octets in URLs"},"content":{"rendered":"
<\/p>\n

SAP CPI challenge – continuation of the learning<\/h2>\n

In the recently concluded CPI challenge<\/strong><\/span><\/a>, one part that was missed in most submissions was implementing decoding of percent-encoded octets that were submitted in the query string of the HTTP request. This was not stated as an explicit requirement in the challenge and therefore required the participants to have an implicit understanding of how HTTP URLs work. Those who knew this indeed scored higher in the challenge, gaining bonus points along the way – 2 out of 3 finalists implemented such decoding.<\/p>\n

\n<\/div>\n

As a continuation of the learning spirit encouraged by the challenge, I have recorded the short video below to walk through the concept of percent-encoding, why it is important, and how we can implement the decoding.<\/p>\n

 <\/p>\n

Happy learning!<\/strong>
\n
<\/p>\n