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
Single fetch redirects should probably not use a 200 status code since they might be inadvertently cached...can we return a 202 maybe or is that just as likely to be cached?
The text was updated successfully, but these errors were encountered:
We just published version 2.10.0-pre.0 which involves this issue. If you'd like to take it for a test run please try it out and let us know what you think!
Single fetch redirects should probably not use a 200 status code since they might be inadvertently cached...can we return a 202 maybe or is that just as likely to be cached?
The text was updated successfully, but these errors were encountered: