Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.3
-
Fix Version/s: 1.3.1
-
Component/s: WebDAV Interface
-
Labels:None
-
Environment:Standalone archiva
-
Number of attachments :
Description
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
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.