Re: PyPI JSON API redirect loop for all unpublished packages

2018-05-16 Thread Doug Hellmann
Excerpts from Donald Stufft's message of 2018-05-16 17:09:12 -0400: > > > On May 16, 2018, at 5:06 PM, Doug Hellmann wrote: > > > > > > > > We had an issue testing redirect rules in the OpenStack documentation > > build, so we built a tool to test the .htaccess files. I

Re: PyPI JSON API redirect loop for all unpublished packages

2018-05-16 Thread Donald Stufft
> On May 16, 2018, at 5:06 PM, Doug Hellmann wrote: > > > > We had an issue testing redirect rules in the OpenStack documentation > build, so we built a tool to test the .htaccess files. I don't know > if whereto would be directly useful (maybe you're not using

Re: PyPI JSON API redirect loop for all unpublished packages

2018-05-16 Thread Doug Hellmann
We had an issue testing redirect rules in the OpenStack documentation build, so we built a tool to test the .htaccess files. I don't know if whereto would be directly useful (maybe you're not using Apache?), but I thought I'd mention it in case someone thinks it is. I would also happily take

Re: PyPI JSON API redirect loop for all unpublished packages

2018-05-16 Thread Dustin Ingram
Thanks for the report. I reverted the commit that caused this in https://github.com/pypa/warehouse/pull/4015, however it might take a bit for this to get deployed to PyPI because there's currently a pretty long backlog in Travis due to all the PyPA development happening during the sprints. D. On

Re: PyPI JSON API redirect loop for all unpublished packages

2018-05-16 Thread Alex Becker
Looks like a fix was just merged to Warehouse: https://github.com/pypa/warehouse/pull/4015 I assume that will go out shortly, so this can probably be ignored. On Wednesday, May 16, 2018 at 1:28:23 PM UTC-7, Alex Becker wrote: > > In the last hour I started observing the following loop: > >

PyPI JSON API redirect loop for all unpublished packages

2018-05-16 Thread Alex Becker
In the last hour I started observing the following loop: https://pypi.org/pypi/nonexistant-package/json -> https://pypi.org/pypi/nonexistant-package/json/ -> https://pypi.org/pypi/nonexistant-package/json This is breaking pipenv package resolution for us, since we use 2 different indices and