You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Two people on discord today reported they hit an infinite loop where a shape request with offset=-1 came back with a 200 status but was missing the electric-offset header.
Both had proxies that for one reason or another had stripped the header(s).
Electric doesn't work without its headers so we should give a more helpful clue to people writing middleware on what is wrong.
The error message should look something like:
The response for the shape request to ${url} didn't include the following required headers:
- electric-offset
- etc
This is often due to a proxy not allowing all headers to be returned. See this doc page for more information: https://electric-url.com/something
The text was updated successfully, but these errors were encountered:
Yup, avoiding the scenarios where we hammer the sever with requests in a loop would be good.
There are cases where we do want to call the same URL more than once — eg when trying to sync a table that doesn’t exist yet, we get an error response and keep trying the same URL until the table is created. So there we maybe want more of a backoff.
Two people on discord today reported they hit an infinite loop where a shape request with offset=-1 came back with a 200 status but was missing the
electric-offset
header.Both had proxies that for one reason or another had stripped the header(s).
Electric doesn't work without its headers so we should give a more helpful clue to people writing middleware on what is wrong.
The error message should look something like:
The text was updated successfully, but these errors were encountered: