Christopher Svanefalk
Christopher Svanefalk
Awesome, many thanks for your efforts @lmiller1990
@brian-mann see e.g. https://github.com/cypress-io/cypress/issues/3708#issuecomment-1029050110
> reckon a fix for this, which doesn't involve removing proxying of requests altogether, probably could be to allow us to configure URL roots that should be immediately passed through...
Possible workaround when using Chrome (along with more evidence that this has a real impact on real-life environments): https://github.com/cypress-io/cypress/issues/3708#issuecomment-1710392838
This would be very welcome - we always run in error mode and often see replays starting _exactly_ when the error occurs - completely leaving out important context (API calls...
> Making our backend requests use HTTP/2 would give us a huge performance boost for making requests against servers that support it. For completeness, this is virtually _all_ servers not...
In my case, the logs indicated this is a cookie issue: ``` | 11:24:27 [WARNING] django.security.csrf: Forbidden (CSRF cookie not set.): /api/2/envelope (status_code=403 request=
@hostinqer why not do a soft-backup, start over again with a fresh image, do a restore, and then see if the problem persists?
I meant _start with a fresh image_ - throw everything away, spin up a new server instance, install Sentry, then restore your soft data.
Apologies for the late reply @hubertdeng123 . Yes, the image is otherwise working fine (we are using vanilla on-prem so we are just using the defaul postgres image provided by...