Data not passed in POST request using Node about core HOT 6 CLOSED

I just looked at request/node's code a bit, and I don't think it supports data as an object. The tests seem to indicate it can accept one of core's ReadableStreams or a string, though it's not clear to me from request/node's code how a string would work either, since it just immediately calls request.end.

At the very least I'd say try serializing that object to a x-www-form-urlencoded string yourself and see if that works. (core's UrlSearchParams or node's querystring can help with that.)

If this makes it inconsistent with the xhr provider then it's probably something we should look at...

from core.

Ah, ok.

So this works then.

var params = new UrlSearchParams(DATA);
var paramsString = params.toString();
// using dojo-core/request
function getDojoToken(callback){
  dojoRequest.post('https://www.arcgis.com/sharing/rest/oauth2/token/',{
    responseType: 'json',
    query: paramsString
  }).then(function(results) {
    console.log('dojo request results', results.data);
  });
}

I suppose I can do a has('host-node') check around a function to create the parameters so this can be used in multiple environments.

Thanks for clearing that up!

from core.

I think that @kfranqueiro is correct. Strings aren't handled properly as the 'data' field. That test is looking at the response data, not the data received by the server. I'll fix that, but supporting object literals is not currently supported and I can't find evidence that this is planned since it can be accomplished via JSON.stringify(DATA).

from core.

I don't know/remember off the top of my head, but I suspect it might be intentional, given that people have different opinions/requirements as to whether their objects should be serialized simply as JSON, or as www-form-urlencoded strings.

from core.

I think the intention would be that they would use the filterRegistry to deal with whatever needs they have specifically for post processing of requests.

from core.

Issued PR #127 to correct issue where options.data not being sent to server when it contained a non-stream.

from core.