Re: Post data encoding itself

The short answer is that the encoding should not matter as it is not
logically changing the POST body content.

If the encoding does matter for some obscure reason then your best bet
is to manually assemble the body as a string to your exact liking and
then supply this string to http.post (instead of the current parameter
table).

There is a separate inconsistency in your code in that the Content-Type
header declares the body as a JSON object but you seem to be aiming for
"application/x-www-form-urlencoded" instead.

Cheers,
nnposter
_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/