[
https://issues.apache.org/jira/browse/JCR-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16069789#comment-16069789
]
Tobias Bocanegra commented on JCR-4154:
---------------------------------------
thanks [~reschke]. the old behaviour was to repeat the param name as filename:
https://issues.apache.org/jira/browse/JCRVLT-186?focusedCommentId=16066124&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16066124
I don't think the filename is really used, so your solution is sufficient.
however, a quick test revealed:
{noformat}
Content-Disposition: form-data; name="/tmp/test.png/jcr:content/jcr:data";
filename="/var/folders/jg/7xdlx73d12g8qrwmkynvxqrc0000gn/T/bin66635
{noformat}
which is somewhat private information from the client sent to the server. i.e.
the location of my temp file. so maybe it's better to use a neutral filename
like, {{"dummy.bin"}} or repeat the {{paramName}} like before.
> davex upload of binaries broken
> -------------------------------
>
> Key: JCR-4154
> URL: https://issues.apache.org/jira/browse/JCR-4154
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-spi2dav
> Affects Versions: 2.15.0, 2.14.0
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Labels: candidate_jcr_2_14
> Fix For: 2.16, 2.15.5
>
> Attachments: JCR-4154.diff, JCR-4154.diff
>
>
> When using the remoting servlet, upload of binaries seems to be broken (see
> JCRVLT-186).
> Seems this is caused by the multi part handling on the server assuming the
> presence of a filename parameter in content-disposition (which was present
> before we switched to heepclient 4.*)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
