On 5/7/13 8:07 AM, XMPP Extensions Editor wrote:
> The XMPP Extensions Editor has received a proposal for a new XEP.
>
> Title: HTTP over XMPP transport
>
> Abstract: This specification defines how XMPP can be used to transport HTTP
> communication over peer-to-peer networks.
>
> URL: http://xmpp.org/extensions/inbox/http-over-xmpp.html
I'm not yet convinced of the need for this extension, but if we're going
to proceed with it then I strongly recommend re-using the syntax from
XEP-0131.
Thus...
OLD
<iq type='get'
from='[email protected]/browser'
to='[email protected]'
id='1'>
<req xmlns='urn:xmpp:http' method='OPTIONS' resource='*'
version='1.1'>
<header name='Host' value='clayster.com'/>
</req>
</iq>
<iq type='result'
from='[email protected]'
to='[email protected]/browser'
id='1'>
<resp xmlns='urn:xmpp:http' version='1.1' statusCode='200'
statusMessage='OK'>
<header name='Date' value='Fri, 03 May 2013 13:52:10 GMT-4'/>
<header name='Allow' value='OPTIONS, GET, HEAD, POST, PUT,
DELETE, TRACE'/>
<header name='Content-Length' value='0'/>
</resp>
</iq>
NEW
<iq type='get'
from='[email protected]/browser'
to='[email protected]'
id='1'>
<req xmlns='urn:xmpp:http' method='OPTIONS' resource='*'
version='1.1'>
<headers xmlns='http://jabber.org/protocol/shim'>
<header name='Host'>clayster.com</header>
</headers>
</req>
</iq>
<iq type='result'
from='[email protected]'
to='[email protected]/browser'
id='1'>
<resp xmlns='urn:xmpp:http' version='1.1' statusCode='200'
statusMessage='OK'>
<headers xmlns='http://jabber.org/protocol/shim'>
<header name='Date'>Fri, 03 May 2013 13:52:10 GMT-4</header>
<header name='Allow'>OPTIONS, GET, HEAD, POST, PUT, DELETE,
TRACE</header>
<header name='Content-Length'>0</header>
</headers>
</resp>
</iq>
