NimbostratusI'm not positive without testing but, based on your code snippet, it looks like when a client requests abc.def.gov/engagement, the switch condition is true and the first IF condition is true. That causes the first HTTP::redirect statement to execute. But since there is no ELSE condition for the second HTTP::redirect, my guess is that it, too, is executing, causing the reset condition. Some browsers may ignore a second redirect but Chrome may be sensitive to it and reset the connection.
Either add an ELSE condition for the second redirect, or add a return after the first redirect to prevent the second from also executing.
