Thank you for your reply. Yes, the problem is solved with a subdomain, but for some reason, I don’t want to use a subdomain. That’s why I was challenged and I’m looking for a solution.
Thank you for giving a solution with the help of path.
@stbu that’s mentioned in the article I linked above.
But as that article mentions, that is often not a solution that will work, because if the upstream app ever crafts any paths in the HTML response, it may have the /blog prefix missing, breaking all URLs or causing JS/CSS assets to fail to load.
The upstream app must be aware of the path prefix being stripped, otherwise it can’t build paths correctly.
So that’s why subdomains are the recommended solution, because it avoids this problem entirely.