This JIRA is meant to align Spring Data for Pivotal GemFire with Pivotal's over arching goal of securing all network communications, e.g. using HTTPS rather than plain text HTTP.
In addition, in cases where the user may have opted for unsecure, plain text HTTP connections, then it still may be necessary to support HTTP redirects, since a corporate network (e.g. Router) may respond to a non-secure HTTP request with a 3xx Status Code instructing the HTTP client to redirect to a secure HTTP endpoint
John Blum opened DATAGEODE-192 and commented
This JIRA is meant to align Spring Data for Pivotal GemFire with Pivotal's over arching goal of securing all network communications, e.g. using HTTPS rather than plain text HTTP.
In addition, in cases where the user may have opted for unsecure, plain text HTTP connections, then it still may be necessary to support HTTP redirects, since a corporate network (e.g. Router) may respond to a non-secure HTTP request with a 3xx Status Code instructing the HTTP client to redirect to a secure HTTP endpoint
Referenced from: commits 25701a9, d4f8a96, 9710130, b54e3b6
Backported to: 2.1.9 (Lovelace SR9)
The text was updated successfully, but these errors were encountered: