I fully agree with you that just putting the url in the body and doing
magic based on the file extension and HEAD request isn't a good solution.
oob isn't of any help here either because it doesn't include the content
type or the file size. (and especially not extended information like
resolution
On 1/29/16 9:38 AM, Anurodh Pokharel wrote:
Hi all,
In the process of implementing XEP-0363 (HTTP file uploads
http://xmpp.org/extensions/xep-0363.html) in Monal, I've come to the
realization that it would make a lot of sense to include MIME content
type and size in the message stanza. I've d
Thanks, I think out of band data on messages is an easy solution.
HEAD is part of the HTTP spec but is not uncommon for it to be blocked on
server configurations. Additionally, depending on the way the media is
served (e.g. via a script that hides the actual path) you may not actually
get any inf
Hi,
On 01/29/2016 05:38 PM, Anurodh Pokharel wrote:
> In the process of implementing XEP-0363 (HTTP file uploads
> http://xmpp.org/extensions/xep-0363.html) in Monal, I've come to the
> realization that it would make a lot of sense to include MIME content type
> and size in the message stanza.
There wasn't much interest I think. But I have to say that I didn't
take the initiative either :-)
http://mail.jabber.org/pipermail/standards/2013-September/027992.html
On Fri, Jan 29, 2016 at 5:38 PM, Anurodh Pokharel wrote:
> Hi all,
> In the process of implementing XEP-0363 (HTTP file upload
Hi all,
In the process of implementing XEP-0363 (HTTP file uploads
http://xmpp.org/extensions/xep-0363.html) in Monal, I've come to the
realization that it would make a lot of sense to include MIME content type
and size in the message stanza. I've done a bit of searching and I haven't
found any