Tableau Public两种URL语法差异及404问题技术咨询

Let's unpack exactly why you're seeing that 404 error while your client can access the link just fine.

Key Syntax Differences #

First, let's clarify the URL characters in question:

• #! is the standard fragment identifier format Tableau Public uses for its single-page app (SPA) routing. This tells Tableau's frontend to load the specific view/dashboard associated with the route that follows.
• %23! is the URL-encoded version of #!. The %23 is how the # character is represented when it's encoded (since # has special meaning in URLs as the start of a fragment).

Why the Client Can Access It (But You Can't) #

The critical difference here is login state:

• When your client is logged into their Tableau Public account, Tableau's backend/frontend has special logic to handle "imperfect" URLs. It likely recognizes the encoded %23! as a mistake and automatically decodes it to #!, allowing the correct route to load.
• For unauthenticated users (like you accessing the link without being logged into their account), Tableau's public access layer doesn't perform this automatic correction. It treats %23! as part of the actual route path, which doesn't exist—hence the 404 error.

What About ?publish=yes? #

As you tested, this query parameter doesn't affect availability. It's a temporary parameter used during the Tableau publishing workflow. Once the content is published, this parameter is irrelevant—Tableau ignores it whether it's present or not, so it's not the cause of your 404.

Summary of the Issue #

Your client's original link fails for unauthenticated users because the encoded %23! isn't recognized by Tableau Public's public-facing routing system. Only logged-in users trigger the error correction that maps %23! back to the valid #! format. To fix this, you can manually replace %23! with #! and remove the ?publish=yes (though removing it isn't strictly necessary) to get a link that works for everyone.

内容的提问来源于stack exchange，提问作者Conner M.