request.headers returns empty json about worktop HOT 6 CLOSED

This is plain JavaScript mechanics.

You can verify this in your Chrome devtools console too.

Headers (and Map, and FormData, and ...etc) print an empty {} by default. You have to actually convert it to an object or array of pairs first.

Options:

console.log([...req.headers]);
console.log(Object.fromEntries(req.headers));

Hope that helps!

from worktop.

Perfect. Thanks!

from worktop.

Can't this be fixed with a proxy that does the conversion?

from worktop.

Not going to happen, sorry. Sticking with raw primitives as they're being converged upon everywhere

from worktop.

I don’t understand, aren’t proxies just magical enough to let noobs play without understanding what’s happening underneath?

from worktop.

It's overhead and boilerplate needed for hardly any gain, and you end up reimplementing a bunch of stuff you would have gotten for free. Plus most people probably wouldn't need it, so it all goes to waste.

Doing Object.fromEntries(req.query) is straight forward and working with native JS APIs, as designed.

from worktop.