You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Brian Fox (JIRA)" <ji...@apache.org> on 2010/12/15 15:43:01 UTC
[jira] Created: (IVY-1255) Possible bug in Ivy's maven resolver is
causing massive amounts of redundant traffic
Possible bug in Ivy's maven resolver is causing massive amounts of redundant traffic
------------------------------------------------------------------------------------
Key: IVY-1255
URL: https://issues.apache.org/jira/browse/IVY-1255
Project: Ivy
Issue Type: Bug
Components: Maven Compatibility
Affects Versions: 2.1.0
Reporter: Brian Fox
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVY-1255) Possible bug in Ivy's maven resolver is
causing massive amounts of redundant traffic
Posted by "Brian Fox (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox updated IVY-1255:
---------------------------
Attachment: ivy.log.gz
> Possible bug in Ivy's maven resolver is causing massive amounts of redundant traffic
> ------------------------------------------------------------------------------------
>
> Key: IVY-1255
> URL: https://issues.apache.org/jira/browse/IVY-1255
> Project: Ivy
> Issue Type: Bug
> Components: Maven Compatibility
> Affects Versions: 2.1.0
> Reporter: Brian Fox
> Attachments: ivy.log.gz
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-1255) Possible bug in Ivy's maven resolver
is causing massive amounts of redundant traffic
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973961#action_12973961 ]
Maarten Coene commented on IVY-1255:
------------------------------------
Do you also have any information regarding the configuration of the Ivy clients?
> Possible bug in Ivy's maven resolver is causing massive amounts of redundant traffic
> ------------------------------------------------------------------------------------
>
> Key: IVY-1255
> URL: https://issues.apache.org/jira/browse/IVY-1255
> Project: Ivy
> Issue Type: Bug
> Components: Maven Compatibility
> Affects Versions: 2.1.0
> Reporter: Brian Fox
> Attachments: ivy.log.gz
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.