Problem

-- When Gateway is acting as a client (initiator) and connecting to a remote HTTP/S site, if it receives a 301 (Moved Permanently) response, Gateway does not use the new location, but will continue trying to use the original one.

Resolution

* The remote site definition should be modified manually to point to the new location. (This also avoids the possibility of a man-in-the-middle attack that could redirect an outbound transfer to a compromised location.)

* Beginning with 6.14.1 SP4, this behavior is modified: a 301 response is treated like a 302, so that Gateway will attempt to follow the new location but will still leave the remote site definition unchanged.