Node/Express app: req.headers is undefined

isaac-hinmanPRO

8 months ago

I'm running a Node+Express app via a Docker container on Railway – we're migrating over from Render.

To my surprise, various endpoints are 500ing because req.headers.authorization is undefined. In fact, req.headersitself is undefined.

This is extremely unexpected/unusual behaviour, and I assume it is related to some proxy layer that Railway has in place.

I've searched around as much as I can, but found nothing helpful. I'd like to be pointed in the right direction.

Not a great DX when getting started on a platform.

Awaiting User Response

4 Replies

isaac-hinmanPRO

8 months ago

Please ignore: this is user error on our side. I suspect many of these kind of issues are


8 months ago

I'm glad you were able to solve it, if this was a platform issue we would be hearing it from just about every user

I'm curious, what was the issue?


Status changed to Awaiting User Response railway[bot] 8 months ago


isaac-hinmanPRO

8 months ago

The issue was a very tricky one, to do with Bun internals/transpilation. The worst kind of bug...


Status changed to Awaiting Railway Response railway[bot] 8 months ago


8 months ago

Then kudo's to you for solving it so fast!


Status changed to Awaiting User Response railway[bot] 8 months ago