API Query Parameters Forcing Input to Lowercase

Wappler General Bugs
,
#1

Wappler Version : 1.9.2
Operating System : Windows 10 and OS X 10.14.3

Expected behavior

Please don’t force lowercase the input of this field as some API query parameters are CaSe sensitive.

Actual behavior

Because the input of this field is forced to lowercase, any API whose query parameters are CaSe sensitive are not supported. Have a look:

This works:
https://api.iextrading.com/1.0/stock/aapl/quote?displayPercent=true

This does NOT work:
https://api.iextrading.com/1.0/stock/aapl/quote?displaypercent=true

API_force_lowercase

Thanks guys!

:sunglasses:

1 Like
#2

This is currently by design because of the many mistakes people make by typing query parameters in mixed case. So we force them to be all lowercase and also valid.

We have a lot of problems with this in the past with server connect and parameters passing.

Also currently the query parameters are store as html attributes which are also required to be lowercase.

Usually most of the API’s also use lowercase parameters to avoid confusion and user mistakes. But seems you have found one API that is not that smart… :slight_smile:

Will investigate if we can make exceptions for special API’s that require it.

2 Likes
#3
#4

Thank you, @George

#5

I agree with you. You shouldn’t force lowercase the input in API action.

This works:
https://www.googleapis.com/identitytoolkit/v3/relyingparty/verifyCustomToken?key=[xxx]
returnSecureToken=true

This doesn’t:
https://www.googleapis.com/identitytoolkit/v3/relyingparty/verifyCustomToken?key=[xxx] returnsecuretoken=true

Thanks

1 Like
#6

Do you plan to fix it?

Thanks

#7

Yes we are going to fix this

#8
#9

A post was split to a new topic: Posting JSON with API Action