VS Code Extension Marketplace link shows 404 on first access before redirecting correctly #496
Description
When accessing the Accord Project VS Code extension via its Azure DevOps Marketplace URL (as linked from the documentation), the page initially displays a 404 – Page not found error. After clicking “Go back home”, the correct VS Code extension page loads successfully. This behavior is confusing and may mislead users into thinking the extension is unavailable.
Expected Behavior
The VS Code extension marketplace page should load correctly on the first attempt.
Users should not encounter a 404 error when visiting a valid extension link from the documentation.
Current Behavior
The marketplace link initially shows a 404 – Page not found error.
Clicking “Go back home” redirects the user to the correct VS Code extension page.
This creates unnecessary friction and confusion for first-time users.
Possible Solution
Verify and update the marketplace URL used in the documentation.
Add or fix server-side redirection so the extension page resolves correctly on the first load.
Ensure guest/unauthenticated access does not trigger an incorrect 404 response.
Steps to Reproduce
Open a browser (logged in or guest mode).
Click the VS Code extension marketplace link from the Accord Project documentation.
Observe the 404 – Page not found error.
Click on “Go back home”.
Notice that the correct VS Code extension page is displayed.
Context (Environment)
This issue affects discoverability and user trust. As a contributor and GSoC 2026 applicant, I was trying to explore the VS Code extension through the official documentation. The initial 404 error makes it appear that the extension link is broken.
Desktop
OS: Windows 11
Browser: Google Chrome
Version: Latest stable
Detailed Description
The Azure DevOps Marketplace URL for the Accord Project VS Code extension appears to be valid but intermittently fails to resolve on the first request, returning a 404 error page. The extension page becomes accessible only after a manual user action (“Go back home”), suggesting a routing, caching, or redirection issue rather than a missing resource. This can negatively impact new users accessing the extension through documentation or shared links.
Possible Implementation
Add a fallback redirect when a valid extension itemName is detected.
Improve link validation and testing in documentation to catch marketplace URL issues.
Consider automated checks for broken external links in docs.
Happy to submit a PR if a documentation link update or redirect fix is needed.