On Wednesday, August 13, 2014 1:17:05 AM UTC+2, Roger Lovato wrote: > I have a F5 bigip configured to make reverse https proxy to a Linux box > with Gitlab working only in port 80 (http). > > Apparently works fine, but some pages that needs to redirect to other > pages, like login page that I have access in https://gitlab.mydomain.com, > I've been redirected to http://gitlab.mydomain.com/users/sign_in and not > https://gitlab.mydomain.com/users/sign_in. This also happens in other > pages that need to redirect. This problem happens only internal redirects > inside Gitlab. > > (INTERNET)----->(BIGIP F5 https)----->(GITLAB CentOS http) >
I noticed similar things, but this was behind a NetScaler. Which is also normal. If the app runs on http it generates links and what not with http. I think everything would be a workaround if you try rewrite things. No matter if on GitLab server or on the F5 Big-IP device. You would even have to rewrite response bodies. Which has other problems. I am not aware of a option to tell GitLab that it thinks it is https even if it is running on http. The simplest thing is to configure https on GitLab and have your load balancer talk https to GitLab. This can even be a self signed cert. It is only from F5 to GitLab and thus transparent to the user. This works just fine for me. -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/1f0082f5-e61c-4f12-a37a-98e77c6baee4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
