[
http://jira.codehaus.org/browse/MRM-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MRM-1356:
------------------------------
Fix Version/s: 1.3.1
thanks, I didn't realise Maven 3 had changed that. We'll look into it.
You may want to grab the source for 1.3 and comment out the check. IF you have
a patch to improve it with a test it'd certainly help push this along.
> 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
