TYPO3 Core

Seems still relevant in TYPO3 v9.5.27
Tested with TYPO3 9.5.27
PHP 7.4
and site config
routeEnhancers:
PageTypeSuffix:
type: PageType

what have I done?¶

Configured a PageType in TypoScript to use a different view and other settings. For example generate a xml view of a news page or prevent JavaScript and CSS files from being loaded on certain pages or use AjaxReuests.
Do not map the PageTyp in site config.

what did I expect?¶

A certain page https://example.org/foo/?type=1 would be rendered with the page config of typeNum = 1.

what happened?¶

The page is rendered with the configuration of default page setup. Looks different.

technical remarks¶

especially <f:link.page pageUid="{currentUid}" pageType="1"> an <f:uri.page pageUid="{currentUid}" pageType="1"> loaded only the page with default configuration. I guess f:link.action does it the some way.
https://example.org/?uid=x&type=1 would work, but that is not the output of the mentioned ViewHelper

The problem is that the default suffix "/" automatically sets the page type to 0.
When calling "https://example.org/foo?type=1" (without the trailing slash) the type is correctly set.

(Removing the mapping from '"/": 0' does not fix this!

I still think it would be very beneficial to be able to override the page type with the "?page" GET parameter, because that makes it easier to build Ajax URLs from the current URL.

This problem exists here on TYPO3 10.4.22.