ShawnFumo

@albehrens Did you ever find a solution to this? I think we're seeing the same issue...

@albehrens Thanks. I don't think that'll work for us unfortunately. For security reasons, we need fairly short inactivity timeouts. So we have access tokens that expire within minutes and refresh...

@albehrens I was able to find a temporary solution (temp since I'm using some non-public parts of the library), though still not sure why it is happening in the first...

@albehrens Actually, figured out the issue. What we're both doing is turning off the default body parsing, which makes body be a stream and for some reason writeHead on the...

@albehrens In theory you'd grab the if/else block and stick it right before the return proxy part (leaving out the res.send). There's a chance it won't work for you since...

Just as a note to others, we have a system in place where a user logging in through SSO, may have permissions to certain resources, which is determined on their...

@adamjmcgrath Thanks. Before you delve too much more, while I don't know if the header is still a good idea or not, we just realized the bigger issue that is...

@adamjmcgrath I don't believe that's the issue. The lambda going through CloudFront is the same one that handles `handleAuth()` (and under the same behavior path), so if no cookies could...

I got it working! It isn't ideal: I'm importing stuff from the dist folder directly (I'm assuming getConfig and CookieStore aren't part of the public interface?), and having to reconstruct...

It seems I was actually right about the `on-headers` thing. On AWS, the callback never gets called: ``` console.log('***before using onHeaders') onHeaders(res, () => console.log("***hey, writing the headers")) res.status(response.status).send(response.body); ```...