[
https://issues.apache.org/jira/browse/BUILDR-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Boisvert resolved BUILDR-573.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.4.6
Patch applied. Thanks Mathias!
{code}
boisvert@smudge:~/git/buildr$ git commit -m "BUILDR-573 HTTP upload PUT request
with incorrect Content-Type (Mathias Doenitz)" .
[trunk ab3dd3a] BUILDR-573 HTTP upload PUT request with incorrect Content-Type
(Mathias Doenitz)
2 files changed, 2 insertions(+), 1 deletions(-)
boisvert@smudge:~/git/buildr$ git svn dcommit
Committing to https://svn.apache.org/repos/asf/buildr/trunk ...
M CHANGELOG
M lib/buildr/core/transports.rb
Committed r1082211
{code}
> upload via HTTP send PUT request with incorrect Content-Type header
> -------------------------------------------------------------------
>
> Key: BUILDR-573
> URL: https://issues.apache.org/jira/browse/BUILDR-573
> Project: Buildr
> Issue Type: Bug
> Components: Core features
> Affects Versions: 1.4.5
> Reporter: Mathias
> Fix For: 1.4.6
>
> Attachments: fix.patch
>
> Original Estimate: 5m
> Remaining Estimate: 5m
>
> When uploading via HTTP buildr sends PUT requests with "Content-Type:
> application/x-www-form-urlencoded", which is incorrect and can lead to issues
> with some repository managers (e.g. Nexus 1.9).
> The fix would be to either send no Content-Type header at all (in which case
> the server is allowed to guess the Content-Type) or send
> "application/octet-stream".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
