Actions
Feature #88361
closed
Site error handling: "Show content from page" for 404 should render page directly
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Site Handling, Site Sets & Routing
Target version:
Start date:
2019-05-15
Due date:
% Done:
0%
Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:
Description
Currently displaying a 404-page with "content from page" (pointing to a page by its uid) results in curl fetching the content to display. That's another roundtrip, adds load to the webserver and in some environments might even cause additional problems (https-validation not working, ...).
Instead it would be great to render that page-content directly.
Updated by Stefan Neufeind over 5 years ago
- Subject changed from 404-handling: "Show content from page" should render page directly to Site error handling: "Show content from page" for 404 should render page directly
Updated by Stefan Neufeind over 5 years ago
- Related to Bug #86935: Cannot fetch 404 page with simple base added
Updated by Stefan Neufeind over 5 years ago
As pointed out in https://forge.typo3.org/issues/86935#note-9 external fetches might also run into problems if the page has a protection configured (http-basic-auth, ...). Direct rendering would avoid that.
Updated by Benni Mack over 5 years ago
- Status changed from New to Accepted
- Target version set to Candidate for Major Version
I have a PoC for that already, and it works, but has side effects in v9 ofc. v10 is clean and possible.
Updated by Benni Mack about 3 years ago
- Related to Bug #94402: Don't issue second HTTP request for error handling added
Updated by Benni Mack about 3 years ago
Updated by
Actions