Hey guys, what could be causing this infinite refr...
# support-questions-legacy
m
Hey guys, what could be causing this infinite refresh? Is there any information I can provide
r
Hey! What are the response headers from the refresh api?
m
it seems that my server is down. responding with 203
but it cause supertokens to keep calling refresh
is there a way to prevent this in production later on?
r
Right. It seems that redwood returns a 203 in this case. Which is weird. Normally when a server is down, it should return a >= 500 status code
You could open an issue about this on our GitHub. We can provide a way to get around this. But really, I think it’s a redwood issue.
m
does 203 mean , we should retry the api call?
r
Well, 203 means that the request was successful, but that the response was modified by a proxy
So if the proxy modifies the response to remove the set-cookie header (which may be happening in this case), it can cause this issue
m
I see. Is there a simple toggle flag to prevent this infinite cycle?
or it's complicated?
r
It’s complicated.
m
I see. I hope api won't go down 🙂
so is the problem the 203, or the modified remove set cookie header?
r
Well, both.
I’m not sure what happens in redwood js side that yields a 203. So hard to say
But as I said, if you open an issue about this, we can do something about it on our side
4 Views