XEP-0363 HTTP Upload error
See original GitHub issueI am having trouble sending file with the http_upload using the latest Jsxc. The following is my setup and observation. Would appreciate if someone can help on this.
OS: Windows Server XMPP Client: Gajim 0.16.5 Browser: Firefox 53.0.2 Jsxc version : jsxc v3.2.0-beta.2 - 2017-04-28
OS: CentOS 7.3 XMPP Server: ejabberd 17.04
- Test using Gajim 0.16.5 with XMPP Server works well with the http upload
- Test using Jsxc fails when sending File
It is strange that the image and document link sent from Gajim does not appear in the user2 window in Jsxc. Is this normal ?
The following is the trace i’ve got from firefox:
Details for the highlighted line: [Headers]
[Parameters]
<body rid='18170630' xmlns='http://jabber.org/protocol/httpbind' sid='ef9a8114c5016e4eae18e75379f7d59f41b4b858'><iq to='upload.my.domain.com' type='get' xmlns='jabber:client' id='e54d0baa-28a6-4535-9877-5402622089ec:sendIQ'><request xmlns='urn:xmpp:http:upload'><filename>default.JPG</filename><size>1646</size></request></iq></body>
[Response]
<body xmlns='http://jabber.org/protocol/httpbind'><iq xml:lang='en' to='user1@my.domain.com/example' from='upload.my.domain.com' type='result' id='e54d0baa-28a6-4535-9877-5402622089ec:sendIQ' xmlns='jabber:client'><slot xmlns='urn:xmpp:http:upload'><get>http://my.domain.com:5443/upload/99200b9f75dd114a7e239482e8440f3cc67e2ef0/5jr952GAlunI81bD0O84siBtbIxFxUnwWDiqjADo/default.JPG</get><put>http://my.domain.com:5443/upload/99200b9f75dd114a7e239482e8440f3cc67e2ef0/5jr952GAlunI81bD0O84siBtbIxFxUnwWDiqjADo/default.JPG</put></slot></iq></body>
Details for the next line with the method “OPTIONS”: [Headers]
Request URL shows : http://my.domain.com:5443/upload/99200b9f75dd114a7e239482e8440f3cc67e2ef0/5jr952GAlunI81bD0O84siBtbIxFxUnwWDiqjADo/default.JPG
[Parameters] Blank
[Response] Blank
Issue Analytics
- State:
- Created 6 years ago
- Comments:17 (6 by maintainers)
Top GitHub Comments
fre. 19. mai 2017 kl. 16.23 skrev skyfox675 notifications@github.com:
@skyfox675 is your issue maybe related to #526?