[
http://jira.codehaus.org/browse/WAGON-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg closed WAGON-284.
-------------------------------
Resolution: Won't Fix
Assignee: Mark Struberg
Actually it's not a problem imo.
Using the 100-continue mechanism would mean that _every_ request would need to
be sent twice!
The 100-continue logic is to send a request upfront if the server is willing to
accept the data at all. The server will most likely respond with a
HTTP_CONTINUE (100) ret code. In this case the client sends the real request.
IF we'd like to implement that, then it would only make sense to do this solely
for big uploads. Which is a bit of a problem for the stream based wagons.
> Artifacts are uploaded twice in the case of HTTP redirection
> ------------------------------------------------------------
>
> Key: WAGON-284
> URL: http://jira.codehaus.org/browse/WAGON-284
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http
> Affects Versions: 1.0-beta-6
> Environment: Debian unstable, Sun JDK 6.0u14
> Reporter: Alex Hvostov
> Assignee: Mark Struberg
> Priority: Minor
> Fix For: 1.0
>
>
> When deploying to an HTTP (not DAV) repository, if the request is redirected,
> the artifact is uploaded twice: once for the original request, and then again
> at the redirect location.
> Please consider using "Expect: 100-continue" when uploading, so as not to
> waste bandwidth in the case of a redirect. See RFC 2616 section 8.2.3.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
