-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
audit suggestion: track failed HTTP requests #3128
Comments
HTTP failures result in console errors, so #2836 should actually address this as well. |
@patrickhulce good point! I may try to extract changes from #2836 and provide new PR to add only this audit. |
fixed by #2836 |
@alekseykulikov you could do that, though we may then have some interesting overlap between the two. It's a little awkward so we favor keeping the 2836 audit all-together. does that work for you? |
During page execution: ajax requests may fail, or images/js/css didn't exist and returned 404. That may be a solid recommendation to fix.
It's similar to the tracking of javascript errors #3109, 0 failed HTTP request is a valid expectation.
The text was updated successfully, but these errors were encountered: