The Reverse proxy settings are a bit tricky to understand and often drive to wrong protocol detection.
Place Drupal behind a reverse proxy and do not set $settings['reverse_proxy'] : no warning is display.
Add an information on the status page displaying what info Drupal extract from the headers.
$request->getScheme();
$request->getHost();
$request->getClientIp();
Display a warning if $request::HEADER_X_FORWARDED_FOR is present but $request->getTrustedProxies() is not set (and link to reverse proxy doc).
Display an error if $request->getTrustedProxies() is set but $request->isFromTrustedProxy() return false.
If $request->getTrustedProxies() is set display the trusted proxy list $request->getTrustedProxies()
Add info about reverse_proxy on status page.
Add a line in status page.
None.
None.
Add status about
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This issue is a bit more critical since
https://www.drupal.org/sa-core-2023-004: →
the phpinfo page doesn't display anymore the request headers.
The status page should return the following order HTTP headers in order to setup or debug the reverse proxy settings : REMOTE_ADDR, HTTP_X_FORWARDED_*, HTTP_HOST, SERVER_PORT, REQUEST_SCHEME.