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!

    ProGet OData V2 API

    Scheduled Pinned Locked Moved Support
    5 Posts 4 Posters 15 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.
    • R Offline
      rick.kramer_9238
      last edited by

      Hello,
      I wondering if there is an official recommendation on the ProGet API V2 (OData) and V3-JSON? All our Nuget conncectors are V3 and I have not users report a problem with the ProGet V2. I am asking because there is warning banner on the ProGet home page that states the NuGet feed is using deprecated OData (V2) queries.

      atrippA 1 Reply Last reply Reply Quote 0
      • atrippA Offline
        atripp inedo-engineer @rick.kramer_9238
        last edited by

        Hi @rick-kramer_9238 ,

        You should avoid the OData V2 API; it's been deprecated for many years, it's very slow/bulky, and it will likely have bugs in NuGet client, etc.

        If you're getting those warnings, some user/script is making queries that are unsupported by nuget.org.

        Cheers,
        Alana

        1 Reply Last reply Reply Quote 0
        • S Offline
          stefan.seeland_4753
          last edited by

          Does Proget support any information what client uses the OData V2 API?

          atrippA 1 Reply Last reply Reply Quote 0
          • atrippA Offline
            atripp inedo-engineer @stefan.seeland_4753
            last edited by

            Hi @stefan-seeland_4753 ,

            I'm not totally sure what you mean by that... but to clarify, the API is technically called "NuGet API V2 (OData)" and it could be technically used by anything, but probably is just used by the NuGet client or a script/tool that someone wrote that uses it to query the feed.

            There is no information available other than that, so you'd need to disable the feature on the feed (and therefore cause an error on the client) or use some kind of access monitoring tool to see where the query is coming from (IP address, etc).

            Cheers,
            Alana

            1 Reply Last reply Reply Quote 0
            • steviecoasterS Offline
              steviecoaster
              last edited by

              If you're using Chocolatey at a version lower than 2.0.0 then there was only NuGet v2 support. Since 2.0.0 we've added support for NuGet v3. We also send chocolatey cli in the headers of the request, so you would be able to monitor the traffic and determin which traffic is originating from that tool.

              But as others mentioned, you wouldn't be able to determine much from the ProGet side.

              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