You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 30, 2019. It is now read-only.
Cpanel parameters are case sensitive - like FOO and foo are completely different things. The crazy part here is that you can make an API or function call with both params versions and only one will succeed, e.g:
call modifyacct with rs param to change an account's theme. Request will succeed but the account won't be modified
make the same call but use RS instead of rs. Request will succeed and account's theme will be changed
What if we normalize parameters? Lumberg should make the right request regardless of params' case.
The text was updated successfully, but these errors were encountered:
Snuggie is another example of an API that makes awful decisions when it comes to naming parameters. For that, we allow the normal, yet ugly params that match the upstream API credentials. Then we allow convenience params that Snuggie converts.
So, for your example above, something like:
defblah(params={})params[:RS]=params.delete(:rs)ifparams.has_key?(:rs)
...
end
Cpanel parameters are case sensitive - like
FOO
andfoo
are completely different things. The crazy part here is that you can make an API or function call with both params versions and only one will succeed, e.g:modifyacct
withrs
param to change an account's theme. Request will succeed but the account won't be modifiedRS
instead ofrs
. Request will succeed and account's theme will be changedWhat if we normalize parameters? Lumberg should make the right request regardless of params' case.
The text was updated successfully, but these errors were encountered: