Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+Redirects\s+http\s+to\s+https\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+Redirects\s+http\s+to\s+https\s*$/: 8 ]

Total 8 documents matching your query.

1. Re: [lvs-users] Redirects http to https (score: 1): Author: Brian <ba221400@xxxxxxxxx>; Date: Tue, 30 Jul 2013 23:14:47 -0400; Thanks for all of the replies. I continued to play around this this and I was definitely over-thinking it and now have it working. I've updated my question on Server Fault with more information: http; /html/lvs-users/2013-07/msg00036.html (14,546 bytes)
2. Re: [lvs-users] Redirects http to https (score: 1): Author: Dennis Jacobfeuerborn <dennisml@xxxxxxxxxxxx>; Date: Wed, 24 Jul 2013 13:00:35 +0200; Have you checked that when you enable the redirect that "lvs.htm" can still be reached from the directors system using both port 80 and 443? It looks like you real servers get disabled because the he; /html/lvs-users/2013-07/msg00035.html (12,591 bytes)
3. Re: [lvs-users] Redirects http to https (score: 1): Author: Anders Henke <anders.henke@xxxxxxxx>; Date: Wed, 24 Jul 2013 11:06:50 +0200; Hi Brian, I'm not sure what you mean, and probably some other folks as well :-) IPVS/LVS works on OSI layers 2-4, depending on what you're exactly looking at: -Direct Routing: LVS receives a packet f; /html/lvs-users/2013-07/msg00034.html (12,115 bytes)
4. Re: [lvs-users] Redirects http to https (score: 1): Author: Samy Ascha <samy@xxxxxx>; Date: Wed, 24 Jul 2013 10:05:13 +0200; Brian, The simplest solution, and the one I would implement, is to reserve a special URL for the ldirectord HTTP(80) check. This URL should not be matched by your 301 redirect configuration, but rath; /html/lvs-users/2013-07/msg00033.html (11,549 bytes)
5. Re: [lvs-users] Redirects http to https (score: 1): Author: Malcolm Turnbull <malcolm@xxxxxxxxxxxxxxxx>; Date: Wed, 24 Jul 2013 07:54:55 +0100; Brian, LVS operates at Layer 4 and therefore has no capability to do Layer 7 re-directs. You would need to use HAProxy (or preferably your application cluster to do it.) -- Regards, Malcolm Turnbull.; /html/lvs-users/2013-07/msg00032.html (9,601 bytes)
6. Re: [lvs-users] Redirects http to https (score: 1): Author: Brian <ba221400@xxxxxxxxx>; Date: Tue, 23 Jul 2013 23:36:41 -0400; Thanks Samy. I am not sure what you mean though--I'm not doing anything specific to ldirectord with the 301. I'm simply doing a redirect with my web server to send http to https. I'm still stuck on t; /html/lvs-users/2013-07/msg00031.html (13,785 bytes)
7. Re: [lvs-users] Redirects http to https (score: 1): Author: Samy Ascha <samy@xxxxxx>; Date: Mon, 22 Jul 2013 10:18:31 +0200; Brian, Don't know the finer details, but I recon LVS would not take the time to follow redirects, and maybe it doesn't even make sense to do so. I think you should just alter your ldirectord check to; /html/lvs-users/2013-07/msg00030.html (11,961 bytes)
8. [lvs-users] Redirects http to https (score: 1): Author: Brian <ba221400@xxxxxxxxx>; Date: Sat, 20 Jul 2013 11:03:15 -0400; I'm trying to redirect all http traffic to https. I am using nginx and LVS with http now without any issues. Using a standard nginx 301 redirect results in LVS setting my real server's weight to 0. H; /html/lvs-users/2013-07/msg00029.html (9,907 bytes)

Current List: 1 - 8
Page: [1]