Dispatcher Cache Issue

Hi @randeep_virk ,

It's possible that the dispatcher is not caching the page when accessed via the domain name due to a configuration issue. Here are some things you can check:

1. Verify the dispatcher configuration: Check the dispatcher configuration to ensure that the domain name is correctly configured. Make sure that the `virtualhosts` section in the dispatcher configuration file (`dispatcher.any`) includes the domain name and that it is mapped to the correct publisher.

2. Check the DNS configuration: Verify that the DNS configuration for the domain name is correct. Ensure that the domain name is correctly mapped to the IP address of the publisher.

3. Check the request headers: When accessing the page via the domain name, check the request headers to ensure that they are correctly configured. Make sure that the `Host` header is set to the domain name and that it matches the `virtualhosts` configuration in the dispatcher.

4. Check the dispatcher logs: Check the dispatcher logs to see if there are any errors or warnings related to the domain name. The logs may provide more information about the issue.

5. Clear the dispatcher cache: If the above steps do not resolve the issue, try clearing the dispatcher cache and accessing the page again via the domain name. This will force the dispatcher to cache the page again and may resolve any caching issues.

By checking the dispatcher configuration, DNS configuration, request headers, and logs, you should be able to identify and resolve any issues preventing the dispatcher from caching the page when accessed via the domain name.

Hi @randeep_virk 
Please check if there is a different config for localhost virtualhost

@randeep_virk Did you find the suggestions from users helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.