abac abandonment academic fraud AI protection b2c business Business integration China shipping chrome Chrome malfunction corporate sustainability cost effectiveness Database implementation Dichotomical approach display manager distanced from Econometric modelling economics EU goods EU LAMP hosting Explanation scarcity framework franchise Fraudulent security gitflow Gmail project management flow hdd headphones HTML form HTTP headers Income sustainability javascript JIRA Layered economics ligthweight mobile banking NATO infringements Postman direction profit margin Public casualty public hotspot r&d RPG SFTP competitive advantages Smartphone infringements sme steam Steam Gentoo gaming supemarket Trance music staged shows umidigi unix Vocabulary enriching wifi Wifi durability xiaomi

Chrome not rendering basic HTML output with proper HTTP headers

Bionics diseases, such as human bod infection of Covic19 - coronavirus - is a tangible threat debugging web applications, especially in terms of core application like Chrome rendering caps; denominating malfunction behavior it is infringing and impeding Twig frontend rendering workflow. Developer is urged to look for another solution, making PHP development more fragile than usual.

It’s astonishing, if not perplexing, that ordinary Chrome isn’t grasping the contents of a totally usual HTML, emitted via local web server:

HTTP/1.1 200 OK
Host: localhost:8080
Date: Sun, 29 Mar 2020 13:24:27 GMT
Connection: close
X-Powered-By: PHP/7.2.29
Accept: application/x-www-form-urlencoded
Accept-Encoding: utf8
Access-Control-Allow-Credentials: true
Access-Control-Allow-Origin:
Access-Control-Allow-Headers: X-Requested-With, Content-Type, Accept, Origin, Authorization
Access-Control-Allow-Methods: GET, POST, PUT, PATCH, DELETE, OPTIONS
Cache-Control: no-store, no-cache, must-revalidate, max-age=0
Cache-Control: post-check=0, pre-check=0
Pragma: no-cache
Content-type: text/html; charset=UTF-8
<html>
<head>
    <title>User display</title>
</head>
<body>
	<header>
		<div class="jumbotron">
	<h1 class="display-4">User display</h1>
	<p class="lead">This is hackathon at home product - notes taking app</p>
	<hr class="my-4">
	<p>It's based on Slim with webpack, susy and layered views dashboard.</p>
</div>

	</header>
	    
	<footer>
		<div class="container-fluid">
	<div class="card" style="width: 18rem;">
		<div class="card-body">
			<h5 class="card-title">Porfolio</h5>
			<p class="card-text">pbgroup.com blog and projects digests - SME eCommerce, eFinance & eCredits development.</p>
		</div>
	</div>
</div>
	</footer>
	http://dist/main.js
</body>
</html>

Screen image:

HTML not rendered in Chrome browser, emitted via web server URL (bar)

I have never seen this before, very strange case. It’s not a first time with a bride of a girlfriend, but it looks more terrifying – like a phpunit sequence of failures in a bug trial.

->withAddedHeader('Accept', 'text/html')

besides

->withHeader('Accept', 'application/x-www-form-urlencoded')

to response object doesn’t help. Anyway it’s not a sound check, inspecting ability to see the responded result, but a a major glitch of Chrome process rendering.

HTTP API debugging tools like Postman is rendering this content correctly:

Mis-interpreted HTML content, correctly displayed in Postman preview tab.

Weird it may look like, it’s an unusual behavior of Chrome browser, indicating connections to some Covid19, Coronavirus statements.

%d bloggers like this: