Closed suresh-khurdiya-epam closed 9 months ago
Loading failure logs are not seen in console(Journalctl) but same failure logs can be seen in web inspector console.
var xhr = new XMLHttpRequest(); xhr.onreadystatechange = function() { if (this.readyState == 1) { console.log('opened state') } if (this.readyState == 2) { console.log('headers received state') } if (this.readyState == 3) { console.log('loading state') } if (this.readyState == 4 && this.status == 200) { console.log('done state'); document.getElementById("demo").innerHTML = this.responseText; } };
xhr.open("GET", "https://localhost:8000/info.txt", true); xhr.send();
After about 60 sec, error is seen in web inspector: "Failed to load resource: Could not connect: Socket I/O timed out"
Actual results: Error is not seen in journal file
Loading failure logs are not seen in console(Journalctl) but same failure logs can be seen in web inspector console.
Replication path/steps: Trigger JS error from web inspector:
var xhr = new XMLHttpRequest(); xhr.onreadystatechange = function() { if (this.readyState == 1) { console.log('opened state') } if (this.readyState == 2) { console.log('headers received state') } if (this.readyState == 3) { console.log('loading state') } if (this.readyState == 4 && this.status == 200) { console.log('done state'); document.getElementById("demo").innerHTML = this.responseText; } };
xhr.open("GET", "https://localhost:8000/info.txt", true); xhr.send();
After about 60 sec, error is seen in web inspector: "Failed to load resource: Could not connect: Socket I/O timed out"
Actual results: Error is not seen in journal file
Expected results: Error must be seen in journal file