TYPO3\CMS\Extbase\Core\Bootstrap::handleFrontendRequest()

Complexity

Conditions	12
Paths	73

Size

Total Lines	61
Code Lines	29

Duplication

Lines	0
Ratio	0 %

Importance

Changes

0

<?php
    protected function handleFrontendRequest(ServerRequestInterface $request): string
    {
        $extbaseRequest = $this->extbaseRequestBuilder->build($request);
        if (!$this->isExtbaseRequestCacheable($extbaseRequest)) {
            if ($this->cObj->getUserObjectType() === ContentObjectRenderer::OBJECTTYPE_USER) {

The condition $this->cObj->getUserObjectType() === TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer::OBJECTTYPE_USER is always false.

                // ContentObjectRenderer::convertToUserIntObject() will recreate the object,
                // so we have to stop the request here before the action is actually called
                $this->cObj->convertToUserIntObject();
                return '';
            }
        }

        // Dispatch the extbase request
        $requestHandler = $this->requestHandlerResolver->resolveRequestHandler($extbaseRequest);
        $response = $requestHandler->handleRequest($extbaseRequest);
        if ($response->getStatusCode() >= 300) {
            // Avoid caching the plugin when we issue a redirect or error response
            // This means that even when an action is configured as cachable
            // we avoid the plugin to be cached, but keep the page cache untouched
            if ($this->cObj->getUserObjectType() === ContentObjectRenderer::OBJECTTYPE_USER) {

The condition $this->cObj->getUserObjectType() === TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer::OBJECTTYPE_USER is always false.

                $this->cObj->convertToUserIntObject();
            }
        }
        // Usually coming from an error action, ensure all caches are cleared
        if ($response->getStatusCode() === 400) {
            $this->clearCacheOnError();
        }

        // In case TSFE is available and this is a json response, we have
        // to take the TypoScript settings regarding charset into account.
        // @todo Since HTML5 only utf-8 is a valid charset, this settings should be deprecated
        if (($typoScriptFrontendController = ($GLOBALS['TSFE'] ?? null)) instanceof TypoScriptFrontendController
            && strpos($response->getHeaderLine('Content-Type'), 'application/json') === 0
        ) {
            // Unset the already defined Content-Type
            $response = $response->withoutHeader('Content-Type');
            if (empty($typoScriptFrontendController->config['config']['disableCharsetHeader'])) {
                // If the charset header is *not* disabled in configuration,
                // TypoScriptFrontendController will send the header later with the Content-Type which we set here.
                $typoScriptFrontendController->setContentType('application/json');
            } else {
                // Although the charset header is disabled in configuration, we *must* send a Content-Type header here.
                // Content-Type headers optionally carry charset information at the same time.
                // Since we have the information about the charset, there is no reason to not include the charset information although disabled in TypoScript.
                $response = $response->withHeader('Content-Type', 'application/json; charset=' . trim($typoScriptFrontendController->metaCharset));
            }
        }

        if (headers_sent() === false) {
            foreach ($response->getHeaders() as $name => $values) {
                foreach ($values as $value) {
                    header(sprintf('%s: %s', $name, $value));
                }
            }
        }
        $body = $response->getBody();
        $body->rewind();
        $content = $body->getContents();
        $this->resetSingletons();
        $this->cacheService->clearCachesOfRegisteredPageIds();
        return $content;
    }