Appended path segement on site base is ignored

[tgaertner]

Given a site base like "https://mydomain.com/path".

Expect that the request is called against "https://mydomain.com/path/-/opcache/reset"

Current behaviour: the request is called against: "https://mydomain.com/-/opcache/reset"

[mbrodala]

Actually the current behavior is correct since the Opcache is global and not related to any site, base or TYPO3 in general.

Do you see specific issues with the current behavior?

[tgaertner]

We have a custom branch deployment with deployer on staging servers where path to public webroot is suffixed like "/123_feature", that means the base without that suffix is not callable by the webserver, since there is no typo3/index.php at that level.
Considering the path from our site base would solve that issue. In general it should not harm any other setup if the path is taken into the URI (most installations don't have a path anyway...)

[tgaertner]

This could also happen to suffixed domains for languages - so its releated to #18

[tgaertner]

The root of the problem is, if TYPO3 can not resolve the site it will throw an exeption. Maybe an other way to solve this is to place the middleware before the site resolving... not sure about this....