I was having trouble using now.js when running node behind an nginx reverse_proxy.
This little patch solves that problem by enabling users to pass a custom host/port combination to Now when initializing so it fills out /nowjs/now.js with the correct information instead of some bogus localhost and strange port configuration.
ericz
commented
13 years ago
Hey,
I was having trouble using now.js when running node behind an nginx reverse_proxy.
This little patch solves that problem by enabling users to pass a custom host/port combination to Now when initializing so it fills out /nowjs/now.js with the correct information instead of some bogus localhost and strange port configuration.
Cheers, ~Swizec