TYPO3 Core

I got the same problem.

Calling https://myDomain.com/xyz does not result in a 404 error. Instead the homepage is shown.
The same behaviour on all subpages. Calling https://myDomain.com/subpage/xyz just shows https://myDomain.com/subpage.

This is an example enhancer configuration which triggers this (i only have this one active to avoid interferences with other enhancers):

  PowermailPlugin:
    type: Extbase
    extension: Powermail
    plugin: Pi1
    routes:
      -
        routePath: '/{test}'
        _controller: 'Form::form'
        _arguments:
          test: foo/test

My understanding is that the above configuration only gets resolved if the request includes the arguments with namespaces like this:

tx_powermail_pi1[controller]=Form
tx_powermail_pi1[action]=form
tx_powermail_pi1[foo][test]=xyz

But instead by simply calling https://myDomain.com/xyz somehow the action and controller and even the prefix foo of the arguments test magically appear and of course the configured route matches in this case:

I didnt even set a defaultController, but even in this case it should not match because the argument tx_powermail_pi1[foo][test] would not exist, right?

What am i missing here? How does typo3 resolve this?

Hi guys,

Any development on that issue? It's a critical one for SEO...

Thanks.

Hey Philipp,

Philipp Lüdtke wrote in #note-6:

My understanding is that the above configuration only gets resolved if the request includes the arguments with namespaces like this:

tx_powermail_pi1[controller]=Form
tx_powermail_pi1[action]=form
tx_powermail_pi1[foo][test]=xyz

I think there is a misunderstanding, and your example shows this properly. The request only contains the URL. The request does not contain the arguments, but the plugin expects them, for this reason, the Extbase Enhancer fills your "www.example.com/my-page-does-not-exist" information INTO the arguments for plugin, not vice versa.

• a site for www.example.com
• the best-match for the page (which is "/" = your site root)
• and the powermail argument "tx_powermail_pi1[foo][test]=my-page-does-not-exist" which then the plugin can use.

Your example with powermail actually is a good example why you should define: "limitToPages", and a prefix such as "/submit" in your "routePath: '/submit/{test}'", or alternatively you define a requirement for "test" (such as https://docs.typo3.org/m/typo3/reference-coreapi/11.5/en-us/ApiOverview/Routing/AdvancedRoutingConfiguration.html#simple-enhancer) or even better an aspect, to define your own logic what values are allowed for "{test}".

Hope that helps!

Closing this issue. In case you thinks there's still something that needs to be changed in the core, please feel free to reopen this issue with providing details how to reproduce the issue - that includes the complete route configuration, code for potential custom aspect mappers, instruction used to generate a URL and/or the corresponding URL that lead to a misbehavior.