Getting 404 on some json files

[JMorinPS]

Hi there,

I have some issues during my composer update

Looks like some JSON files are not find anymore (not always the same package)

However, the funny thing is that with a curl (or with my browser), I can reach the file

I suspected first some issues with BunnyCDN and location because all my errors were with response header CDN-RequestCountryCode: BE` matching my virtual machine location But I can reproduce it with France or even US location

Any issue on your end ? Best

[stof]

You are accessing the Composer v1 metadata endpoints of packagist, which are deprecated and are being shutdown. See https://blog.packagist.com/deprecating-composer-1-support/ and https://blog.packagist.com/shutting-down-packagist-org-support-for-composer-1-x/ for the details.

[Seldaek]

I can confirm https://packagist.org/p/akamai-open/edgegrid-client$447ea167fd0153f6ba6a6f8c05eddff6b8e09a7e8f5c957820dc9accb7296eb1.json is 404 right now, but it seems like it's having issues with one of our origin servers returning 404s for these /p/ files, I just don't get why yet.

I reduced cache for now to be able to debug this but anyway these files should be fetched from the repo.packagist.org domain, where there should be no such issue.

I suggest you switch to the correct domain (if you're on Composer 1 make sure you define a custom repository like "repositories": {"packagist.org": {"type":"composer", "url": "https://repo.packagist.org"}}. But ideally if you use latest Composer 1.10 it should have the correct repo by default https://github.com/composer/composer/blob/1.10/src/Composer/Config.php#L76-L82 so I am not sure what you do to be using the top level domain there..

[Seldaek]

Closing here.. I think I have found the root cause but it doesn't really matter as we are shutting down v1 metadata access next Monday anyway.