allow 'options.origin' to be a regexp

[zaggino]

usage would be: options.origin = /^(.*\.)?github\.com$/ to allow cors from any subdomain of github.com

implementation probably something like

if (options.origin.test && options.origin.test(req.headers.origin)) value = req.headers.origin
else value = ''

https://github.com/troygoode/node-cors/blob/master/lib/index.js#L25

[etiktin]

@zaggino that's a good idea.
Technically you can already use regex to test for a match by setting origin to a function, but I think that directly assigning a regex will make the code concise and easier to understand.

I suggest to also add an option to assign an array to origin to support an origin whitelist.

Supporting regex and array will mean that you hardly never need to use the function syntax (the only reason to use it will be for complex scenarios).

@troygoode, what do you think?

[troygoode]

@zaggino @etiktin yes, I like the idea. there is an open pull request (#48) that I'll merge once a unit test that covers the functionality has been added

[troygoode]

this has shipped to npm as 2.7.0

cc @zaggino @etiktin @alex94puchades

[wilfredjonathanjames]

Are we able to get this feature documented?

[erikbaxstrom]

Are we able to get this feature documented?

Since this issue comes up high in google search results and the actual documentation doesn't, yes. It was documented.
Configuration Options