Skip to content

Conversation

@rubensworks
Copy link
Contributor

This was because header.js tried to add headers after the response was already sent.

Copy link
Contributor

@RubenVerborgh RubenVerborgh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But don't we need the other headers?

in any case, it's an architectural problem that the headers are sent by the next handler.

@rubensworks
Copy link
Contributor Author

Hmm, yes, you're right. I'll fix that right away!

@rubensworks rubensworks force-pushed the fix/login-header-error branch from 8cf8a92 to 6a0b760 Compare December 10, 2018 09:48
@rubensworks
Copy link
Contributor Author

I've reverted my last change, as it broke a bunch of things.

So actually my initial fix was correct. All necessary headers are present, becauseheader.js is called before the get.js.
next() not being called here anymore is consistent with the databrowser and file logic.

@RubenVerborgh
Copy link
Contributor

Sweet, GitHub now shows force pushes.

@kjetilk kjetilk merged commit c15bf82 into nodeSolidServer:release/v5.0.0 Dec 10, 2018
@ghost ghost removed the in progress label Dec 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants