LB3 Migration Issue: Headers Already Sent When Page Reloads #8788
Unanswered
cjbeery24
asked this question in
LB3 Migration
Replies: 1 comment
-
Adding this to my application seems to keep the node process from crashing, allowing pages to refresh with no issues. Not sure this is a good idea, though.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've got a separate front end application that is calling my Loopback 4 API endpoints. When the front end application's page is refreshed too quickly, my Loopback 4 API produces this error:
Some information about the Loopback 4 app:
This contains a partially migrated Loopback 3 application in the "lb3app" directory in the root of the project. Some of the front end application's API calls are hitting the Loopback 4 endpoints and some of them are hitting the Loopback 3 endpoints.
I'm not really even sure how to start debugging this. Any suggestions?
EDIT:
It looks like this is a similar issue with no resolution:
#7196
Beta Was this translation helpful? Give feedback.
All reactions