jsonp-wrapper-pmb v0.1.1

jsonp-wrapper-pmb

A suggestion and utility for easily wrapping your API JSON reply in JSONP packaging.

Cheat sheet

/some/api -> {"foo":"bar"}
/some/api?jsonp=myApp.render -> myApp.render({"foo":"bar"});
/some/api?jsonp=myApp.recv:motd:123 -> myApp.recv('motd','123',{"foo":"bar"});
/some/api?jsonp=console.debug:reply -> console.debug('reply',{"foo":"bar"});

API

This module exports one function:

jsonpWrap(cbName)

cbName is the untrusted config string that describes the JSONP packaging to be used. It's usually a client-provided query argument, potentially controlled by an attacker, and thus it is jsonpWrapper's responsibility to handle it safely and securely.

Returns an array of two (potentially empty) strings: What to print before your regular API result, and what to print after. This way you have full choice: If your server API needs to concatenate the reply, you can easily use the .join() method, and if instead you use streams, you can print each component individually.

• If anything about cbName is invalid, two empty strings are returned.
• A false-y (e.g., empty) cbName is invalid. This avoids wasting CPU cycles if the request doesn't even want JSONP.
• Valid characters in cbName are a subset of the Unicode block "Basic Latin", specifically: Letters (A-Za-z), digits (0-9), low line (aka underscore; _) full stop (.), and colon (:).
• The colon character divides the string into callback name and arguments.
• An empty callback name is invalid.
• Arguments, if any, will be single-quoted and inserted as early arguments to the callback.
  • Example use case: Adding timestamps so the receiver can easily discard late replies to already-obsolete requests.
  • Example use case: Use the same receiver function for multiple data topics.
  • Security: Due to the harsh restriction on valid characters, we can blindly put single quotes and don't have to worry about complex quoting rules.

Usage

see test/usage.mjs.

License

ISC