Solved: Why doesn't XML-to-JSON policy set the Content-Len... - Page 2

Report Inappropriate Content · 01-27-2016 02:09 PM

I am converting an inbound request from XML to JSON before passing to my backend Node.js App and I noticed some strange behavior, like not being able to parse the body or even just echo it back. Then I noticed the error: "request size did not match content length" from the Node.js App.

After further experimenting I noticed that XML-to-JSON policy does not set the Content-Length header. If I manually set it to the correct value, the Node.js App is happy.

I guess I could write a Javascript callout to fix it, but it makes sense for the policy to set it.

@Mike Dunker needs to know this 🙂

Report Inappropriate Content

Work around Javascript policy:

var body = context.targetRequest.body.asJSON;
var len = body.byteLength;
context.proxyRequest.headers['Content-Length']=len;

View solution in original post

Report Inappropriate Content

OK, found another workaround to correctly set the Content-Length even with special characters. One that doesn't rely on Buffer.

Here's my JS policy script that runs after the XML-to-JSON policy:

var obj = context.targetRequest.body.asJSON;
var str = JSON.stringify(obj);
// Attribution: http://stackoverflow.com/questions/23318037/size-of-json-object-in-kbs-mbs#
// Matches only the 10.. bytes that are non-initial characters in a multi-byte sequence.
var m = encodeURIComponent(str).match(/%[89ABab]/g);
var len = str.length + (m ? m.length : 0);
context.targetRequest.headers['Content-Length']=len;

@Mike Dunker, @Birute Awasthi

View solution in original post

Why doesn't XML-to-JSON policy set the Content-Length header?