Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Debugging for Server Side Implementation in Headless architecture - Is there any requirement for QA urls/mboxTrace/mboxDebug

Avatar

Level 2

Hi Team,

 

We have implemented Target Server side using Delivery API and our website follows AEM headless architecture. Wanted to check for the below queries -

1. Will there be any usecases where we will require QA urls to preview the experience or since its server-side and headless, QA urls will not make sense.

2. Will debugging parameters like mboxTrace/mboxDebug/mboxDisable will also not be required in case of server-side and headless implementation

 

Regards,

Disa

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @DisaRas 

 

I think, even if it's server side headless implementation you'll still need QA URLs to test experience before taking activity live and debugging parameters should also work.

View solution in original post

4 Replies

Avatar

Correct answer by
Community Advisor

Hi @DisaRas 

 

I think, even if it's server side headless implementation you'll still need QA URLs to test experience before taking activity live and debugging parameters should also work.

Avatar

Level 2

Hi @Gaureshk_Kodag ,

 

Is there any documentation on how to use QA urls in case of using Delivery API. From my observations, APIs don't return any content until you publish it so not sure how we can leverage QA urls.

 

Regards,

Disa