![]() Here are a few more links and discussion on the this helps. With all of the above, you should be good to go. ![]() At the moment the best solution is in comment #14 - which offers a service implementing OutboundPathProcessorInterface to return '/' for the front page canonical URL. If like us, you've set a node (likely a landing page) as the front page of your site (under Configration -> System -> Basic site settings), then you'll need to be aware of this issue. The next problem you'll face, is ensuring that the canonical URL for the home page of your site is and not. In our case, Nginx is configured by default to forward all headers to fastcgi (PHP-FPM) and so we were receiving the headers fine, however, looking at the HTTP response, both header values and link sources on the page where showing HTTP protocol values for canonical links (not HTTPS) until we enabled the reverse_proxy settings above. If you see values for X-Forwarded-For, and X-Forwarded-Proto - you the protocol portion of your canonical URLs should now be correct. You can test whether PHP (and Drupal) are receiving the required headers by placing a file like proxy-test.php in the root of your Drupal website. There's is an old issue here that would change this setting in Drupal to allow a range, or CIDR address - which would be ideal, but until then you'll need to use the setting above. Since the IP address of AWS's ALB can (and does) change, there's no way to set a fixed IP address for the proxy address. $settings = \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_FOR | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PROTO | \Symfony\Component\HttpFoundation\Request::HEADER_X_FORWARDED_PORT TL DR - assuming your webserver is configured correctly, below are the settings you'll need to add to settings.php for your site: $settings = TRUE ![]() The ALB correctly creates X-Forwarded-For, X-Forwarded-Proto, and X-Forwarded-Port HTTP headers, and so all that's left is to ensure that your web server, and ultimately PHP are configured to receive these headers, and respond accordingly. Revision history Revision revert form Revision delete form With this change, there are now also new granular permissions for granting permission to each the history page and revert and delete forms for block content entities. Block Content is the first entity to use the public facing revision UI. Our sites are deployed via Docker to AWS ECS - with each service registered as a target for an AWS application load balancer (ALB). It is now possible to view, revert and delete block content revisions. Here's a PSA for anyone trying to configure Drupal 8/9 behind a reverse proxy in order to create canonical URLs (in head, and header) that preserve the original remote request protocol - HTTPS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |