Hi,

This issue has been traced to two errant CDN nodes; the provider has
advised us that these nodes have been removed for maintenance.  If
possible, can you confirm that this artifact is now accessible for you?

Regards,
Jason

On Mon, Nov 05, 2012 at 04:05:57PM +0100, Tomasz Pik wrote:

> [ipsilon ss]# wget -dv
> http://repo1.maven.org/maven2/org/springframework/spring-asm/3.1.3.RELEASE/spring-asm-3.1.3.RELEASE.jar
> Setting --verbose (verbose) to 1
> DEBUG output created by Wget 1.13.4 on linux-gnu.
> 
> URI encoding = `UTF-8'
> --2012-11-05 16:01:36--
> http://repo1.maven.org/maven2/org/springframework/spring-asm/3.1.3.RELEASE/spring-asm-3.1.3.RELEASE.jar
> Resolving repo1.maven.org (repo1.maven.org)... 68.232.34.223
> Caching repo1.maven.org => 68.232.34.223
> Connecting to repo1.maven.org (repo1.maven.org)|68.232.34.223|:80...
> connected.
> Created socket 3.
> Releasing 0x00000000012ae740 (new refcount 1).
> 
> ---request begin---
> GET
> /maven2/org/springframework/spring-asm/3.1.3.RELEASE/spring-asm-3.1.3.RELEASE.jar
> HTTP/1.1
> User-Agent: Wget/1.13.4 (linux-gnu)
> Accept: */*
> Host: repo1.maven.org
> Connection: Keep-Alive
> 
> ---request end---
> HTTP request sent, awaiting response... Read error (Connection reset by
> peer) in headers.
> Closed fd 3
> Retrying.
> 
> --2012-11-05 16:02:37--  (try: 2)
> http://repo1.maven.org/maven2/org/springframework/spring-asm/3.1.3.RELEASE/spring-asm-3.1.3.RELEASE.jar
> Found repo1.maven.org in host_name_addresses_map (0x12ae740)
> Connecting to repo1.maven.org (repo1.maven.org)|68.232.34.223|:80...
> connected.
> Created socket 3.
> Releasing 0x00000000012ae740 (new refcount 1).
> 
> ---request begin---
> GET
> /maven2/org/springframework/spring-asm/3.1.3.RELEASE/spring-asm-3.1.3.RELEASE.jar
> HTTP/1.1
> User-Agent: Wget/1.13.4 (linux-gnu)
> Accept: */*
> Host: repo1.maven.org
> Connection: Keep-Alive
> 
> ---request end---
> HTTP request sent, awaiting response... ^C

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to