1. 01 Nov, 2016 1 commit
  2. 20 Oct, 2016 1 commit
  3. 03 Oct, 2016 5 commits
  4. 17 Aug, 2016 6 commits
  5. 13 Aug, 2016 1 commit
  6. 12 Aug, 2016 1 commit
  7. 09 Aug, 2016 1 commit
  8. 01 Aug, 2016 1 commit
  9. 25 Jul, 2016 1 commit
  10. 07 Jul, 2016 1 commit
  11. 04 Jul, 2016 1 commit
  12. 01 Jul, 2016 2 commits
  13. 30 Jun, 2016 1 commit
  14. 11 Apr, 2016 1 commit
  15. 25 Mar, 2016 1 commit
  16. 23 Mar, 2016 3 commits
  17. 21 Mar, 2016 4 commits
  18. 17 Mar, 2016 8 commits
    • Guus der Kinderen's avatar
      OF-1089: Send IQ result only after messages · ad2f9200
      Guus der Kinderen authored
      IQ result should be the last stanza. This way, clients know that the
      last archived message has arrived.
      ad2f9200
    • wroot's avatar
      12a26741
    • Guus der Kinderen's avatar
      Admin Console: prevent NPE on missing user creation date. · 3d569e25
      Guus der Kinderen authored
      Some user providers might not provide a creation date for each user. There's no
      reason that the Admin Console should not be able to cope with that.
      3d569e25
    • Chinmay Dani's avatar
      Outcasts should not be allowed to register with room. · e468a51a
      Chinmay Dani authored
      With the current implementation, any user can send the register IQ to register with
      a room as a 'member'. This also allows outcasts, that were banned from a room, to be
      able to register again as a member, and eventually re-join the room. The solution is
      to prevent outcasts from registering with the room.
      e468a51a
    • Guus der Kinderen's avatar
      OF-1087: Do not add empty-string prefixed namespaces · f60e9152
      Guus der Kinderen authored
      In dom4j, the default namespace of an element cannot be set by adding
      a namespace that has an empty-string prefix. Although the string
      representation of the element will be correct, that namespace is not
      being recognized as the default namespace of the element (instead, it
      is a namespace like any other prefixed namespace, to be used in child
      elements).
      f60e9152
    • Guus der Kinderen's avatar
      OF-1087: Whitespace does not take into account element boundary. · e863a946
      Guus der Kinderen authored
      The original code depends on a whitespace to be present within the limits
      of the element. This is not safe (eg: <message><foo/></message> fails).
      Instead, the closing characters ( > or /> ) of the first element should
      be used, as that's guaranteed to be present.
      e863a946
    • Guus der Kinderen's avatar
      OF-1087: BOSH namespace fix · 3980468e
      Guus der Kinderen authored
      A change introduced in Openfire 3.10.3 (OF-938) changed how the BOSH
      implementation would add default namespace definitions where applicable.
      This new implementation depends on a space from being present in the
      outer stanza. The 'fin' element that's transmitted here is wrapped in
      a message stanza without any attributes ( <message><fin ... ) which
      caused the namespace to be injected in the fin element (where the first
      space was).
      
      This commit adds a 'to' attribute to the wrapping message stanza, to
      allow for users to work around the problem without having to update
      Openfire itself.
      
      The BOSH implementation will be adjusted to account for this in another
      commit.
      3980468e
    • Derek McLean's avatar
      Cannot join room in a cluster after an availability update. · 3c580276
      Derek McLean authored
      When a room occupant sends an availability update to a host in an
      Openfire cluster, other users cannot join the room from other hosts in
      the cluster. The availability update causes the other hosts to lose an
      occupant's role and affiliation. New occupants encounter an NPE when
      joining and are prevented from joining the room. Specifically, the NPE
      occurs when Openfire attempts to send initial presences for current
      occupants.
      
      Remote hosts in the cluster lose the occupant's association because the
      local room simply broadcasts the presence packet for the occupant's
      availability update. Because it is from the client, this packet does not
      have the occupant's role or affiliation. The remote hosts treat the
      presence packet as the occupant's presence without modification.
      
      This fix changes the order in which Openfire handles an availability
      update. First, it updates its local view of an occupant's presence. This
      populates the correct association. Then, it broadcasts the updated
      presence to remote hosts in the cluster.
      3c580276