Tigase Forge
Dashboards
Projects
Pull Requests
Issues
Builds
Packages
Code Search
tigase-http-api
Code
Pull Requests
Issues
List
Boards
Iterations
Builds
Statistics
Child Projects
OneDev 10.9.4
Documentation Support & Bug Report RESTful API Incompatibilities License Agreement Check Update
Projects tigase _server tigase-http-api Issues #41
A problem when i call the HTTP API to Getting the Member List? (#41)
Won't Fix
Wei Sun opened 8 years ago

I met a problem when call the HTTP API to Getting the Member List:

post:

  • req:
    type='get'>
  <query xmlns='http://jabber.org/protocol/muc#admin'>
    <item affiliation='member'/>
  </query>
  • rsp:
    <query xmlns="http://jabber.org/protocol/muc#admin">
        <item affiliation="member"/>
    </query>
    <error code="403" type="auth">
        <forbidden xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/>
    </error>

what should I do to solve this problem?
Wei Sun commented 8 years ago

the rsp like this:

*

<query xmlns="http://jabber.org/protocol/muc#admin">

    <item affiliation="member"/>

</query>

<error code="403" type="auth">

    <forbidden xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/>

</error>

*

thanks！
Andrzej Wójcik (Tigase) commented 8 years ago

Fixed description formatting
Andrzej Wójcik (Tigase) commented 8 years ago

For general questions please use our projects forums.

In this case MUC and HTTP API component are behaving correctly. If I'm correct you are using /rest/stream endpoint (you have not mentioned this).

As you can see packet is sent from HTTP API component with it's address set as a from attribute. Due to that MUC component rejects to return members list as HTTP API component is not a member of a room you are trying to query for list of members (this is correct according to MUC specification).
Wei Sun commented 8 years ago

Andrzej Wójcik wrote:

For general questions please use our projects forums.

In this case MUC and HTTP API component are behaving correctly. If I'm correct you are using /rest/stream endpoint (you have not mentioned this).

As you can see packet is sent from HTTP API component with it's address set as a from attribute. Due to that MUC component rejects to return members list as HTTP API component is not a member of a room you are trying to query for list of members (this is correct according to MUC specification).

thanks a lot！
issue 1 of 1
Type
Bug
Priority
Normal
Assignee
Wei Sun
RedmineID
4905
Issue Votes (0)
Login to vote
Watchers (0)
Reference
tigase/_server/tigase-http-api#41
Please wait...
Page is in error, reload to recover