Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    Problems with Nuget Connector

    Scheduled Pinned Locked Moved Support
    connectorsprogetnugeterrorconnector-filters
    4 Posts 1 Posters 26 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ? This user is from outside of this forum
      Guest
      last edited by

      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

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by

        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.

        1 Reply Last reply Reply Quote 0
        • ? This user is from outside of this forum
          Guest
          last edited by

          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.

          1 Reply Last reply Reply Quote 0
          • ? This user is from outside of this forum
            Guest
            last edited by

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

            1 Reply Last reply Reply Quote 0

            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

            With your input, this post could be even better 💗

            Register Login
            • 1 / 1
            • First post
              Last post
            Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation