If you go to the drupal 7 repository https://packages.drupal.org/7/ you will find that it does not support the packages/list.json url. In that case we just return the packages.json that was returned. This was making retrieving packages.json from a nexus proxy for drupal 7 return a status 500 error.
(brief, plain english overview of your changes here)
instead of failing a get for packages.json from a proxy which does not support the packages/list.json url, this change will instead return the original information from the target repository packages.json response.
This pull request makes the following changes:
when requesting packages.json
if the target repository does not support the url packages/list.json, return the content from packages.json
if the target repository supports the ur packages/list.json, return the information from packages/list.json. This is how previous version (0.0.29 and below) are working
(If there are changes to the UI, please include a screenshot so we
know what to look for!)
no change
(If there are changes to user behavior in general, please make sure to
update the docs, as well)
no change
If you go to the drupal 7 repository https://packages.drupal.org/7/ you will find that it does not support the packages/list.json url. In that case we just return the packages.json that was returned. This was making retrieving packages.json from a nexus proxy for drupal 7 return a status 500 error.
(brief, plain english overview of your changes here)
instead of failing a get for packages.json from a proxy which does not support the packages/list.json url, this change will instead return the original information from the target repository packages.json response.
This pull request makes the following changes:
(If there are changes to the UI, please include a screenshot so we know what to look for!) no change
(If there are changes to user behavior in general, please make sure to update the docs, as well) no change
It relates to the following issue #s: none