01-31-2022, 12:42 PM
Hi again.
Just got an error report from tests of our web applications built with the latest IW version. I analyzed this and it was related to how URL parameters are interpreted. We have a parameter 'k' containing '+' characters which we read directly from WebApplication.RunParams.Values['k'] before (with IW 15.1.15) without problems, but now I get a string with '%2B' substrings instead of '+' (which is it's URL encoded form). So it seems like the (automatic) URL parameter decoding has changed from 15.1.15 to 15.2.49, can you confirm that? Fixing this particular case with e.g. a StringReplace is of course easy, but I would like to know if I should do any changes in the general case where URL parameters (potentially including encoded characters) are involved? (we use that in more places in the web applications)
/Magnus
Just got an error report from tests of our web applications built with the latest IW version. I analyzed this and it was related to how URL parameters are interpreted. We have a parameter 'k' containing '+' characters which we read directly from WebApplication.RunParams.Values['k'] before (with IW 15.1.15) without problems, but now I get a string with '%2B' substrings instead of '+' (which is it's URL encoded form). So it seems like the (automatic) URL parameter decoding has changed from 15.1.15 to 15.2.49, can you confirm that? Fixing this particular case with e.g. a StringReplace is of course easy, but I would like to know if I should do any changes in the general case where URL parameters (potentially including encoded characters) are involved? (we use that in more places in the web applications)
/Magnus