Problems with Nuget Connector

Today I've noticed that the nuget connector is failing with a 400 - Bad Request. It seems to be something on nuget.org side, as this is failing both for v4.0.5 and 3.8.6 with the same configuration. And I'm certain that until a few days ago there where no problems (at least with the v3.8.6).

I've fiddled a little with the Filter and seems the problem is that nuget.org api is not accepting more than 13 criterias. We have a very comprehensive list of allowed packages and as soon as we include more than 13 items it starts failing. For example:

Antlr
bootstrap
CommonServiceLocator
Dapper
EntityFramework
jQuery
jQuery.Validation
log4net
Microsoft.AspNet.*
Microsoft.Bcl.*
Microsoft.Exchange.WebServices
Microsoft.jQuery.Unobtrusive.Validation
Microsoft.Net.Http
Microsoft.Web.Infrastructure

If you remove any of those 14, it works, otherwise the feed page will show

There was an error with a connector:

The remote server returned an error: (400) Bad Request.

Just in case it was a matter of request length, I've tried concatenating two of the names in the same line but that works fine. I still have to check with the networking team just in case the firewall is scrambling the requests but shouldnt be the case.

Has anyone experienced something like that?

Product: ProGet
Version: 4.0.5

As you noted, it's likely a limitation or bug on NuGet.org's end that appeared recently. This has happened from time to time, and if you raise an issue with the NuGet team, they may be able to address it.

We do have a ProGet roadmap item to address this, the full index of NuGet.org context, but it's not trivial as you might immagine.

Thanks Alana. I imagined this could be on the nuget.org side (since I seen it working a few days ago), I'll try to follow it through there.

Today it's working fine. So definitely a temporary outage on nuget.org.