Loader object and form encoded data Issues

[Humair M. <hu...@ho...>]

There are a couple of observations I have made with curl-loader that may need remediation:
1) The loader object does not allow more than 2 tokens when using the RECORDS_FROM_FILE variable even though the documentation indicates you can use up to 16 tokens - I believe by modifying the snprintf call in the client buffer initialization the number of tokens can be increased
2) The application crashes with a segmentation fault at the snprintf call in the client buffer initialization if the post data contains form-encoded values with percent (%) signs. So for example $ is represented as %24 in a form-encoded format and a few of these percent signs will cause the segmentation fault - Not sure what the best way is to handle this will be since % is also the token format character for string replacements
Humair