Unclear Documentation regarding Preview of Hidden Pages

[apus-0]

Following sentence can be found in the documentation:
"If your frontend application passes all cookies from backend correctly you should be able to preview content associated with the root domain."

In my case the backend user cookie is available in the frontend, but i got an 404. This makes sense cause i don't know how to pass the cookie information back to TYPO3 to get the data of the hidden page. I mean the fronted has to send the cookie data to the backend when fetching data? Or am I wrong?

[twoldanski]

Hi @apus-0, what domain setup do you have? You have something like api.your-site.tld (TYPO3) and your-site.tld (FE) or something different?

[apus-0]

first I tried api.your-site.tld (TYPO3) and frontend.your-site.tld (FE) and after your response I also tried api.your-site.tld (TYPO3) and your-site.tld (FE). both appoached didn't work for me. in both cases cookie was set in frontend by TYPO3 when previewing the page, but the in the end i got a 404 page

[twoldanski]

if your main domain is matching and you have setup TYPO3 is api.your-site.tld and fe app is your-site.tld just setup backend cookie (which allows you see hidden pages) to domain .your-site.tld and it should work :)

[lukaszuznanski]

@apus-0 could you send some screenshots of your cookie setup? This would help I believe. We have tested this in several projects, so we can provide some assistance for you.

[apus-0]

Thanks a lot for your replies and for your help.

I set up the cookie domain in the ext_localconf.php of my sitepackage to
$GLOBALS['TYPO3_CONF_VARS']['BE']['cookieDomain'] = getenv('HKC_COOKIE_DOMAIN');

which is
HKC_COOKIE_DOMAIN=.hkc-de.local

and when opening the backend, following cookie is set:

and by opening the fronted app, following cookie is set:

What came into my mind is that i am currently running the site on my local machine, in a docker environment and the domains are no "real" domains. they are only network aliases of docker. Maybe this causes the disfunctionality? At the moment i dont have a test system with "real" domains. But I am working on it. Maybe this solves the problem?

Please let me know, if i should provide further information regarding the set up.

Tank you in advance.

[simonhantha]

Hey guys,
we're currently using the following settings in a project:

• TYPO3 Headless v4.2.7
• configuration: public/typo3conf/system/additional.php we added the new line
  $GLOBALS['TYPO3_CONF_VARS']['BE']['cookieDomain'] = '.testdomain.eu';

Backend e.g. https://api.testdomain.eu/typo3/
Frontend e.g. https://testdomain.eu/de/

When inspecting the cookies on both sites, everything appears correct
Name be_typo_user | Value eyJ0eXA.... | Domain .testdomain.eu | Path / | Expires Session | Size 287 | HttpOnly ✓ | Secure ✓ | SameSite Strict | Priority Medium

However, when accessing the hidden page on the frontend, a 404 error is returned. Do you have any ideas on what might be causing this issue?

Thanks in advance!

EDIT: after reading the other docs and adding proxyReqHeaders: ['cookie'] to typo3.api in the nuxt config, it worked. 🎉

[kitzberger]

I'm currently trying to find out myself why the workspace preview feature on our site broke too.

@simonhantha, I can confirm your solution. Can you explain why it is working?

[simonhantha]

Hi @kitzberger, I assume it works like this:

• Logging into typo3 backend sets the cookie globally for the domain.
• When the frontend makes a request to the backend, then the cookie is not sent by default - so typo3 doesn't know if we're logged in.
• To forward the cookies, the additional setting in the nuxt config is necessary so the user is recognized.