Openfire (ARCHIVED)

S2S is attempted even for subdomains that are known to belong to external components

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 3.5.2
  • Fix Version/s: 3.6.0
  • Component/s: Core
  • Labels:
    None
  • Acceptance Test - Add?:
    Yes
  • Acceptance Test - Entry:
    Hide

    1. Log into the admin console and create a configuration for an external component
    2. From a client send an IQ packet to the subdomain of the external component
    3. Check that no s2s is attempted and that the returned IQ error has the error 'service-unavailable'

    Show
    1. Log into the admin console and create a configuration for an external component 2. From a client send an IQ packet to the subdomain of the external component 3. Check that no s2s is attempted and that the returned IQ error has the error 'service-unavailable'

Description

S2S is attempted even for subdomains that are known to belong to external components. This is the case for external components that are not connected and someone tries to send a packet to the external component. Instead of attempting a s2s we should follow the 'failed to deliver' logic.

Activity

There are no comments yet on this issue.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for igniterealtime.org. Try JIRA - bug tracking software for your team.