[
http://jira.codehaus.org/browse/MRM-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=212788#action_212788
]
Brett Porter commented on MRM-1356:
-----------------------------------
I couldn't reproduce this with Maven 3, but I could with the following:
{code}
curl -v -T -
http://localhost:7777/archiva/repository/test/test/MRM-1356/test-file.txt
* About to connect() to localhost port 7777 (#0)
* Trying ::1... connected
* Connected to localhost (::1) port 7777 (#0)
> PUT /archiva/repository/test/test/MRM-1356/test-file.txt HTTP/1.1
> User-Agent: curl/7.19.4 (universal-apple-darwin10.0) libcurl/7.19.4
> OpenSSL/0.9.8l zlib/1.2.3
> Host: localhost:7777
> Accept: */*
> Transfer-Encoding: chunked
> Expect: 100-continue
>
< HTTP/1.1 100 Continue
testing
< HTTP/1.1 400 Content Header length was -1 but was 0
< Date: Fri, 05 Mar 2010 05:31:16 GMT
< Set-Cookie: JSESSIONID=bxcumg1dehqe;Path=/archiva
< Content-Length: 0
< Server: Jetty(6.1.19)
<
* Connection #0 to host localhost left intact
* Closing connection #0
{code}
> Content Lenght differs : Chunked request
> ----------------------------------------
>
> Key: MRM-1356
> URL: http://jira.codehaus.org/browse/MRM-1356
> Project: Archiva
> Issue Type: Bug
> Components: WebDAV Interface
> Affects Versions: 1.3
> Environment: Standalone archiva
> Reporter: Marc Pasteur
> Fix For: 1.3.1
>
>
> I'm facing some HTTP-400 errors during an artifact upload using maven 3.
> Response text is : HTTP/1.1 400 Content Header length was -1 but was 0.
> No log nor in archiva-audit.log nor in archiva.log
> diving into code I think there is a problem with content-lenght verification.
> With maven 3 the maven-deploy-plugin sent a chunked request so Content-Lenght
> header is empty.
> addMember (ArchivaDavResource) seems comparing request's length and uploaded
> file's length. Can we disable this check in case of chunked request ? is
> there another way to do that ?
> regards,
> marc
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
