i have install the latest dev on my environment running with memcache and varnish i setup in the settings.php base href for my site example.com and stuff like this in the settings.php
$settings['reverse_proxy'] = TRUE;
$settings['reverse_proxy_addresses'] = array('127.0.0.1');
$settings['reverse_proxy_header'] = 'HTTP_X_FORWARDED_FOR';

when i surf the site in the sourcecode i read this ..wrong!

<link rel="alternate" type="application/rss+xml" title="" href="http://example.com:8080/rss.xml" />

Comments

eule’s picture

eule CreditAttribution: eule commented
Issue summary: View changes

blaa typo

fgm’s picture

fgm
Primary language French
Location Paris, France
CreditAttribution: fgm commented
Project: Drupal core » xmlrpc
Version: 8.0.x-dev »
Component: xml-rpc system » Code
Issue summary: View changes

XMLRPC is no longer in core in D8: moved to its own project.

fgm’s picture

fgm
Primary language French
Location Paris, France
CreditAttribution: fgm at OSInet commented
Project: xmlrpc » Drupal core
Version: » 8.0.x-dev
Component: Code » node system

Although this is XML, it does not appear to have had any relationship with XML-RPC: it was just moved here because it was initially posted to the XML-RPC subsystem. Setting back to core.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev
JeroenT’s picture

JeroenT
Primary language Dutch
Location 🇧🇪
CreditAttribution: JeroenT at iO commented
Status: Active » Postponed (maintainer needs more info)
Issue tags: +ddd2022, +Bug Smash Initiative

I tried to reproduce this issue but couldn't. Is this still a problem?

If someone disagrees, or has some steps to reproduce this issue, feel free to reopen.

Wim Leers’s picture

Wim Leers
Location Ghent 🇧🇪🇪🇺
CreditAttribution: Wim Leers at Acquia commented

I don't understand what's wrong? It seems to be implied that http://example.com:8080/rss.xml is wrong — but reverse proxy settings have no impact on the port used in generated URLs? 🤔

These settings only affect \Drupal\Core\StackMiddleware\ReverseProxyMiddleware, not generated URLs.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
CreditAttribution: larowlan as a volunteer commented

This would have to occur via using ['#attached']['feed']

These are the only instances of that in core

            app/core/modules/aggregator/src/Controller  (1 usage found)
                AggregatorController.php  (1 usage found)
                    178 $build['#attached']['feed'][] = ['aggregator/rss', $this->config('system.site')->get('name') . ' ' . $this->t('aggregator')];
            app/core/modules/forum/src/Controller  (1 usage found)
                ForumController.php  (1 usage found)
                    223 $build['#attached']['feed'][] = ['taxonomy/term/' . $term->id() . '/feed', 'RSS - ' . $term->getName()];
            app/core/modules/system/tests/modules/render_attached_test/src/Controller  (1 usage found)
                RenderAttachedTestController.php  (1 usage found)
                    68 $render['#attached']['feed'][] = ['test://url', 'Your RSS feed.'];
            app/core/modules/system/tests/src/Kernel/Common  (1 usage found)
                AddFeedTest.php  (1 usage found)
                    61 $build['#attached']['feed'][] = [$feed_info['url'], $feed_info['title']];
            app/core/modules/views/src/Plugin/views/style  (1 usage found)
                Opml.php  (1 usage found)
                    42 $build['#attached']['feed'][] = [$url, $title];

The first instance is using a relative path of aggregator/rss, the second is using taxonomy/tem, the third and fourth are a test.

The last one is from a views plugin. In that scenario $url is coming from the feed url, which is coming from the URL of the display to which the Opml plugin is attached, which would also be an internal path.

I think we can close this as cannot reproduce

quietone’s picture

quietone CreditAttribution: quietone at PreviousNext commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

I'm reviewing BugSmash issues with the 'Postponed maintainer needs more info' status. This issue is not in my area so I asked in #bugsmash and larowlan responded above. That makes three comments, from three folks, that do not see how to reproduce this problem.

There have been no supporting comments in the 9 years this issue has been open. Therefor, I am closing this as suggested in #16.