#108845Invalid AJAX URL with different BE/entryPoint (sub-)domain
Description
When specifying a different (sub-)domain for BE/entryPoint (e.g. https://typo3-backend.project.ddev.site/) the AdminPanel’s AJAX URL won’t be updated accordingly.
clipboard-202602031410-oxcrq.png
Additionally when trying to manually set the AJAX URL with the new entryPoint’s URL (https://typo3-backend.project.ddev.site/ajax/adminpanel/toggleActiveState?token=807eaafb1a22f8991ac7ce9d5dbdf4de3501c72f), the AJAX request will be blocked due to missing CORS response headers.
P.S. Regarding the AJAX URL, not sure though if this is an issue with the admin panel or a general issue how URLs for the Backend are created.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Files 1
History 2
-
Moritz Ngo changed Duplicates #108473 <span data-processor="relativetime" data-value="2026-03-10T08:57:06+00:00" > 03/10/26, 08:57 </span>
-
Oliver Bartsch commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-10-29T21:59:40+00:00" > 10/29/26, 21:59 </span>
Hey,
thanks for the report and the screenshot. The wrong URL doesn’t come from the admin panel. It comes from the backend UriBuilder: when BE/entryPoint holds a full URL with a different host,
RequestContextFactory::fromBackendRequest()takes the host from the current (frontend) request, andBackendEntryPointResolver::getPathFromRequest()keeps only the path of the entryPoint. The admin panel asks for an absolute path, so it gets/ajax/adminpanel/...with no host, and the browser resolves that against the frontend domain. That is exactly what #108473 describes, and that issue already has a patch under review. I’m closing this one as a duplicate and will follow up there. Once that fix is merged, the admin panel URLs will point to the backend domain automatically.The CORS part is a separate topic. Even with a correct URL, the admin panel would be making a cross-origin request from the frontend domain to the backend domain. That needs CORS headers with credentials, and the backend session cookie would have to be sent cross-site. Core doesn’t support that for a backend on its own domain right now. If you need it, please open a separate feature request.
Cheers, Oli