You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
golink: listen on HTTPS and redirect HTTP traffic (#99)
golink: listen on HTTPS and redirect HTTP traffic
Updates #9Fixes#29
On tailnets with HTTPS enabled golink will serve the primary endpoints via
HTTPS. With HTTPS enabled golink will respond to HTTP traffic with a
separate redirectHandler which redirects requests to their HTTPS equivalent.
Update documented examples of `curl` to include the `-L` flog to follow these
redirects if present.
Add a HTTPS section to the README documenting all of the above.
Signed-off-by: Patrick O'Doherty <[email protected]>
Copy file name to clipboardExpand all lines: README.md
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -146,3 +146,16 @@ If you're using Firefox, you might want to configure two options to make it easy
146
146
with a value of _true_
147
147
148
148
* if you use HTTPS-Only Mode, [add an exception](https://support.mozilla.org/en-US/kb/https-only-prefs#w_add-exceptions-for-http-websites-when-youre-in-https-only-mode)
149
+
150
+
## HTTPS
151
+
152
+
When golink joins your tailnet it will check to see if HTTPS is enabled and
153
+
begin serving HTTPS traffic it detects that it is. When HTTPS is enabled golink
154
+
will redirect all requests received by the HTTP endpoint first to their internal
155
+
HTTPS equivalent before redirecting to the external link destination.
156
+
157
+
**NB:** If you use `curl` to interact with the API of a golink instance with HTTPS
158
+
enabled over its HTTP interface you _must_ specify the `-L` flag to follow these
159
+
redirects or else your request will terminate early with an empty response. We
160
+
recommend the use of the `-L` flag in all deployments regardless of current
161
+
HTTPS status to avoid accidental outages should it be enabled in the future.
0 commit comments