Support adapted vscode api `/vscode/gallery/vscode/{namespace}/{extension}/latest`
It looks like recent versions of VSCode use this endpoint to retrieve some information.
The service currently returns a 302 result to redirect to the error page.
2 things:
- why a redirect instead of an error directly
- support the api endpoint
For the EF: the nginx configuration has been updated to return 404 for these endpoints and needs to be altered once its supported.
an example from the original vscode api: https://marketplace.visualstudio.com/_apis/public//gallery/vscode/streetsidesoftware/code-spell-checker/latest
the service already supports this endpoint /vscode/gallery/{namespaceName}/{extensionName}/latest which seems to contain the same data as the other endpoint
In the interim, I've enabled a rewrite to handle this transparently for open-vsx.org and it's been very beneficial to the site's throughput. The results have high cache rates and the savings obtained from the previous behaviour of 302 to /error are noticeable @ millions of requests/day.
I could not find any documentation about that yet, but the vs marketplace has now different sections, see https://marketplace.visualstudio.com/vscode
it has sections for VS, VSCode and Azure DevOps. Maybe this additional path refers to that.
This is just the behavior of antigravity, which is a VSCode fork, we should reach out to the project to fix that as it is clearly wrong.
Closing that for now as its clearly unwanted behavior from antigravity alone.