-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Minor
-
Affects Version/s: VOMS Clients v. 3.0.1 , VOMS Clients v. 3.0.2
-
Component/s: api-java, clients-native
-
Security Level: Public (Visbile by non-authn users.)
-
None
-
Environment:
VOMS provides two protocols on the same endpoint:
1. legacy VOMS protocol
2. HTTP protocol
Clients first try to connect to the http one and, when the connection fails,
fallback to the legacy one.
Clients v. 3 are confused when the HTTP connection is interrupted on the server side. This was only observed on the VOMS at BNL. The code should
handle correctly this scenario and fall back to the legacy protocol.