Issue Bug Under Review

#111380Admin panel actions fail if the backend entry point has its own host

Oliver Bartsch 11/09/26, 13:08 updated 11/11/26, 09:57

Description

If $GLOBALS[‘TYPO3_CONF_VARS’][‘BE’][‘entryPoint’] points to another origin than the frontend (e.g. https://backend.example.com), the admin panel cannot apply its actions:

  • opening/closing the admin panel (toggle)
  • saving the admin panel settings
  • clearing the page cache / all frontend caches from the Cache module

These actions are sent as XHR calls to backend AJAX routes. Once the backend URLs carry the backend host (see #108473), these calls are cross-origin: the browser does not send the backend session cookie and Core sends no CORS headers, so the requests fail and nothing is applied.

Expected: the admin panel actions work regardless of where the backend entry point lives, ideally by handling them on the frontend origin (same origin as the page showing the admin panel), with CSRF protection and the same permission checks as in the backend.

Reviews 1

History 14