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
At the moment, failedRequests() returns an array. This is great for testing. Yesterday, we had an issue on our test environment, that we could not replicate on local machines or find through testing. As it turned out, the css request failed (server-related issue).
To figure that out we had to duplicate the Browsershot request and redeploy to our test environment. This is far from ideal. Would it be possible to add a feature that allows us to log failed requests with Log in Laravel so we can debug problems in the log file? If possible, it would be great to log failed SSL requests in that, too.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
At the moment,
failedRequests()
returns an array. This is great for testing. Yesterday, we had an issue on our test environment, that we could not replicate on local machines or find through testing. As it turned out, the css request failed (server-related issue).To figure that out we had to duplicate the Browsershot request and redeploy to our test environment. This is far from ideal. Would it be possible to add a feature that allows us to log failed requests with
Log
in Laravel so we can debug problems in the log file? If possible, it would be great to log failed SSL requests in that, too.Beta Was this translation helpful? Give feedback.
All reactions