Skip to main content

Hello,

Assuming a private apps is defined with a single hostname (with the exception of CIDR or wildcard domain) and reachability status is normal, what is the default traffic behaviour if the publishers associated with the app are suddenly unable to each the app? Is the traffic dropped?

Is reachability only relevant in scenarios where a single hostname in an app is defined?

 

The private app FAQ document states the following.

    • When an app is specifies with multiple ports or a port range, the Publisher will use only the first port from the list or range to check availability. For example, port range 70-90 will return unreachable, even if you are listening on port 80, because the only port that will be checked is 70 (this is a known limitation).
    • If an app definition specifies multiple ports and/or port ranges, it will check whether any of them is reachable. For example, if you specify 22, 70-90, if it’s able to reach port 22, it will mark the app as reachable.

Can anyone clarify these statements as they appears to be contradictory. 

 

We have created an app using a single hostname and multiple ports. In traffic logs, we are observing the publisher reachability check running for ALL ports on all publishers. This contradicts what is stipulated above. 

 

Is there any update regarding whether or not reachability can be disabled for specific apps? 

 

Regards,

Simon

Hello,

Assuming a private apps is defined with a single hostname (with the exception of CIDR or wildcard domain) and reachability status is normal, what is the default traffic behaviour if the publishers associated with the app are suddenly unable to each the app? Is the traffic dropped?

Is reachability only relevant in scenarios where a single hostname in an app is defined?

 

The private app FAQ document states the following.

    • When an app is specifies with multiple ports or a port range, the Publisher will use only the first port from the list or range to check availability. For example, port range 70-90 will return unreachable, even if you are listening on port 80, because the only port that will be checked is 70 (this is a known limitation).
    • If an app definition specifies multiple ports and/or port ranges, it will check whether any of them is reachable. For example, if you specify 22, 70-90, if it’s able to reach port 22, it will mark the app as reachable.

Can anyone clarify these statements as they appears to be contradictory. 

 

We have created an app using a single hostname and multiple ports. In traffic logs, we are observing the publisher reachability check running for ALL ports on all publishers. This contradicts what is stipulated above. 

 

Is there any update regarding whether or not reachability can be disabled for specific apps? 

 

Regards,

Simon

 

They are not contradictory statements…

 

The documentation states that only the first defined port is tested for reachability which holds true for both those statements.

 

As for your second statement, I have not personally validated the behavior. So as far as I know the documented tests are accurate.


Reply