You can’t get there with forwarding, as forwarding will, by definition eventually take customers directly to the final location. What you need is reverse proxying.
A reverse proxy works by going to a an address, and having that address proxy the request to a different address at the final site. This does, of-course, mean a double-up of bandwidth use – Once from the client to the proxy, and once from the proxy to the actual server. The flipside of this is you can swap out the proxy for a CDN and have a distributed frontend.
You can build a reverse proxy yourself (lots of ways to do it, Apache has a module to do it, and I believe Nginx and Squid do as well. Its also practical to roll your own if you limit the scope). That said, for the general case most entities use services like Cloudflare or Cloudfront. This has an added advantage of adding DoS protection and other management tools.
Word of caution – if you are planning on distributing content of questionable legality – asking the question you did exposes a lack of knowledge required to avoid getting caught – so don’t do it. While this will be strong protection against end users, it will not by itself prevent agencies backed by government from tracking back to the final site, as there is a lot of infrastructure required of ISPs to help governments/spy agencies – and this is likely to expose the ultimate location if a government deems it worthwhile.