Chrome reload loop

[Polfo]

I have a test page containing the complex_usage_example.php.

When I load the test page with Chrome, chrome continuously reloads the page at high speed (many times a second).

The same occurs when using a different web server.

I tried with a simpler test page, it also loops in reload / refresh

I analyzed the http headers and the page content but could not identify a reason for this looping.

When I disable the php-console extension in the browser, the looping does not occur.

The same looping behaviour also occurs with a much simpler test page.

Any idea what could could cause this looping and how to debug this?

Versions:
Chrome 60.0.3112.90 (Officiële build) (64-bits)
php-console browser client extension 3.0.38
php-console server side PHP 3.1.6
First Web Server: apache, PHP 7.1
Second Web Server: nginx, PHP 7.0
Protocol HTTPS

[Polfo]

The looping stops when the php-console-client cookie is deleted manually in the browser. I document it here for other php-console users who may encounter the same issue.

See:
https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/sdH2OcUUpkE

[Polfo]

The infinite reload loop issue occurs when first activating enableSslOnlyMode(), then commenting that code line and reloading the page. So I suspect there is an issue with the way that php-console client and server treat the redirection. Aspecially since once the reload loop occurs, other pages in the same domain but not using php-console are affected by the reload loop too until the cookie is deleted or the php-console plugin is disabled.

[Chematronix]

This still happens.

The looping stops when the php-console-client cookie is deleted manually in the browser. I document it here for other php-console users who may encounter the same issue.
Didn't help me. Had to reinstall.

See:
https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/sdH2OcUUpkE
Seems unrelated.

I guess this project is just broken beyond help. Good ol' Debug Bar Console still works tho (in WordPress). And Xdebug, of course.