Varnish doesn't work for second language with separate url

[stradd]

Preconditions and environment

Magento ver. 2.4.6-p1

Steps to reproduce

I have a store with 2 languages, each with a separate URL.
Shop -> Web (default) www.example-deutsch.de
Shop -> Web (english) www.example-english.com

The varnish cache is installed and works in the store standard

Answer header store standard

Accept Ranges: bytes
Cache control: no-store, no-cache, must-revalidate, max-age=0
Content encoding: gzip
Content Length: 21909

Content type: text/html; charset=UTF-8
Date: Thu, 27 Jul 2023 11:35:21 GMT
Expires: -1
Grace: none
Pragma: no cache
Server: nginx
Strict Transport Security: max-age=15768000; includeSubDomains
Vary: Accept Encoding
X-Content-Type-Options: nosniff
X-Frame Options: SAMEORIGIN
X-Frame Options: SAMEORIGIN
X Magento Cache Debug: HIT
X-Ua-Compatible: IE=edge
X-Xss Protection: 1; mode=block

If you switch to the Url in english, the Answer Header looks different and the Varnish does not cache the pages either.

Answer header store english
Cache-Control:vmax-age=604800, public, s-maxage=604800
Content encoding:vgzip
Content Length:v21911

Content type:
text/html; charset=UTF-8
dates:
Thu, 27 Jul 2023 11:33:31 GMT
expires:
Thu, 03 Aug 2023 11:33:30 GMT
Link:
</static/version1690280872/_cache/merged/ee58eeb0a3da40bc494f0b1e16c0eedb.min.js>; rel=preload; as=script, </static/version1690280872/_cache/merged/a34774681846944110ee92bbd585d45b.min.css>; rel=preload; as=style, </static/version1690280872/frontend/Saitenhandel/saitenhandel/en_US/css/styles-l.min.css>; rel=preload; as=style, </static/version1690280872/frontend/Saitenhandel/saitenhandel/en_US/css/print.min.css>; rel=preload; as=style, </static/version1690280872/_cache/merged/fonts_a34774681846944110ee92bbd585d45b.min.css>; rel=preload; as=style, </static/version1690280872/frontend/Saitenhandel/saitenhandel/en_US/fonts/opensans/light/opensans-300.woff2>; rel=preload; as=font; crossorigin=anonymous, </static/version1690280872/frontend/Saitenhandel/saitenhandel/en_US/fonts/opensans/regular/opensans-400.woff2>; rel=preload; as=font; crossorigin=anonymous, </static/version1690280872/frontend/Saitenhandel/saitenhandel/en_US/fonts/opensans/semibold/opensans-600.woff2>; rel=preload; as=font; crossorigin=anonymous, </static/version1690280872/frontend/Saitenhandel/saitenhandel/en_US/fonts/opensans/bold/opensans-700.woff2>; rel=preload; as=font; crossorigin=anonymous, </static/version1690280872/frontend/Saitenhandel/saitenhandel/en_US/fonts/Luma-Icons.woff2>; rel=preload; as=font; crossorigin=anonymous
Pragma: cache
Server: nginx
Vary: Accept Encoding
X-Content-Type-Options: nosniff
X-Frame Options: SAMEORIGIN
X-Frame Options: SAMEORIGIN
X Magento Tags:
cat_c,cat_c_6,cat_c_239,cat_c_316,cat_c_272,cat_c_275,cat_c_305,cat_c_327,store,cms_b,mp_smtp_script,cms_b_30,cms_b_31,cms_b_footer_about_us,cms_b_footer_information,cms_b_footer_price,cm s_b_footer_since,cms_p_20
X-Powered-By: PHP/8.1.21
X-Ua-Compatible: IE=edge
X-Xss Protection: 1; mode=block

Expected result

Varnish is also available for second URL and language.

Actual result

Varnish is not available for secondURL and language

Additional information

I use the default.vcl which magento generates itself.
It looks like the varnish isn't enabled for the second URL.

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @stradd. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[maghamed]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @maghamed. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @maghamed, here is your Magento Instance: https://3b5bdbdc01f7608aaf5b17bfac80d6d8.instances-prod.magento-community.engineering
Admin access: https://3b5bdbdc01f7608aaf5b17bfac80d6d8.instances-prod.magento-community.engineering/admin_fe04
Login: b5946f79
Password: d27a4ec0fca3

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hi @stradd,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.

this is for another language store

issue reproducible for store with 2 languages, each with a separate URL, varnish isn't enabled for the second URL

Hence Confirming the issue.

Thanks.