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
So, you see, you have to pass -payload-min=16 to get 32 MB object, and -payload-min=17 to get 64 MB object while the parameter clearly says it is an object size. Why is it encoded in such a weird way then?
Same applies to payload-max. I suggest either renaming this parameter to something better corresponding to the actual meaning, or - even better - allow user to define object min and max size like: -payload-min=1000 - meaning 1 MB
The text was updated successfully, but these errors were encountered:
It says:
I had to look through the code to understand that "payload" is a power of 2 which is then multiplied by 1KB. So, in short:
So, you see, you have to pass
-payload-min=16
to get 32 MB object, and-payload-min=17
to get 64 MB object while the parameter clearly says it isan object size
. Why is it encoded in such a weird way then?Same applies to
payload-max
. I suggest either renaming this parameter to something better corresponding to the actual meaning, or - even better - allow user to define object min and max size like:-payload-min=1000
- meaning 1 MBThe text was updated successfully, but these errors were encountered: