Uploaded image for project: 'Ivy'
  1. Ivy
  2. IVY-1255

Possible bug in Ivy's maven resolver is causing massive amounts of redundant traffic

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 2.1.0
    • None
    • Maven Compatibility
    • None

    Description

      We were investigating suspicious download trends of groovy as reported by the central statistics, and I found some odd behavior from Ivy. I see from many ips massively repeated Head requests spread across many groovy poms and in some cases repeated sequential hits on the same pom milliseconds apart. The attached log shows the behavior from one IP on one day in December. Obviously this is all using the same version of Ivy, but I did notice initially this occurring from many versions.

      Since Maven release artifacts never change, the HEAD request should never be needed, since I assume the file is cached somewhere locally (or you would be doing a get).

      If you need more info from the logs, I'd be glad to help.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            brianf Brian E Fox

            Dates

              Created:
              Updated:

              Slack

                Issue deployment