Anonymous ID: 5ee3fa Jan. 21, 2020, 6:02 a.m. No.7865638   🗄️.is 🔗kun

my browser gives this as a deprecation warning within it's console with settings flipped to show it:

 

Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user’s experience. For more help http://xhr.spec.whatwg.org/ main.js:3086:13

 

the behavior now seems different than it was last bread

last bread I kept getting bad gateway errors for the Vanawa (SP) server

 

this bread it's all code 200 returns for all the requests so far. Last bread there were very many 503 returns.

 

here is what I kept seeing last bread:

GEThttps://8kun.top/vanwanet-verify/index.html

[HTTP/2 502 Bad Gateway 98ms]

 

this bread doesn't have that problem. Wierd.

Anonymous ID: 5ee3fa Jan. 21, 2020, 6:27 a.m. No.7865708   🗄️.is 🔗kun

so now I do get the 502 error return.

and that meant I have to click the 'refresh' button to get the bread to refresh (the auto was not refreshing the page even though ti was shown as on).

The resource is said to have been moved. then a bad gateway error happened. screen grab of messages.

 

OK, the refresh didn't quite do it. I did a full page refresh and got an error in the console as it happened. it was a range error for a date. picture attached.

 

all in all with so much going on and this system being vast . . . I'd say that these kinds of road bump events just show us that we live in the real world. Often we have issues with the flow when too much flow is necessary.