HTTP Servers
From UGCS
(Difference between revisions)
| Line 4: | Line 4: | ||
* Maintain high database uptime for dynamic pages that need to use it | * Maintain high database uptime for dynamic pages that need to use it | ||
* Have acceptable to good performance | * Have acceptable to good performance | ||
| − | |||
* Don't break our users' security models (Allow,Deny based on IP or requiring SSL) | * Don't break our users' security models (Allow,Deny based on IP or requiring SSL) | ||
| + | ** This makes things much more difficult because we have to fake where the connection is coming from. Maybe LVS does this? | ||
==Failover HTTP== | ==Failover HTTP== | ||
Latest revision as of 07:45, 6 June 2010
Goals
The goals behind our web setup are to:
- Maintain high uptime for static pages
- Maintain high database uptime for dynamic pages that need to use it
- Have acceptable to good performance
- Don't break our users' security models (Allow,Deny based on IP or requiring SSL)
- This makes things much more difficult because we have to fake where the connection is coming from. Maybe LVS does this?
Failover HTTP
Failover HTTPS
HTTPS is a lower priority than normal HTTP. Most failover options for it involve
