Tag Info

New answers tagged

0

The software functions much like a Red Hat subscription - the support and current software version are a package deal. Typically the yearly subscription is not cheap costing upwards of several thousand dollars. That being said, you do get what you pay for. The support is world class as Brian mentioned (the sales guys as you discovered maybe not so much) and ...


2

The reason this is occurring is because when the client connects, it establishes a connection to a specific back end server and the F5 will send all subsequent requests using that same connection as long as it exists. When dealing with typical client web requests from human users this solves a bunch of problems and is typical behavior. This behavior ...


0

If a 500 error occurs, this indicates a problem on the web server. The F5 will then simply forward this error along to the connecting client. It will not "re-send" the request of it's own accord. The only way this could happen is if the client re-tries the request. At that point, this request could possibly be load balanced to another pool member, though ...


0

Reading the current status through SNMP has proven the most reliable for me. To enable this you have to start keepalived with snmp support: add -x to the deamon options (see /etc/sysconfig/keepalived on RedHat based systems) and install snmpd. You can then reliably query the status via snmpget -Oq -Ov -v2c -cpublic localhost ...


1

Yes, HAproxy will do that. You'll just need to configure keepalived with all of the virtual IPs that HAproxy will use. You can assign multiple IPs in the virtual_ipaddress block in keepalived.conf: virtual_ipaddress { 192.168.0.10 192.168.0.11 192.168.0.12 192.168.0.13 }


0

I have been trying to find how to migrate my iRules to a Netscaler and I can't seem to find an easy way. I found this conversation that says: There is no denying it, F5 irules are MUCH easier and cleaner then the Netscaler policy-based rules, at least from a management/configuration point of view. In my opinion, this is the one downfall of the netscaler, ...


1

fail_timeout from the NGINX documentation: Sets: the time during which the specified number of unsuccessful attempts to communicate with the server should happen to consider the server unavailable; and the period of time the server will be considered unavailable. So a setting of 5 would mean 10 seconds total (5 timing out, 5 waiting before contacting ...


2

I'm uncomfortable with this Q&A because it hasn't really been established what type of DNS server you're talking about. There are some significant misconceptions when it comes to the resiliency of recursive DNS and it's important that people cruising in via search engines don't walk away from this discussion with a false sense of security. ...


8

Don't load balance your DNS. It's an incredibly light protocol - you'd need an enormous amount of traffic to need more than one box (in which case you'll just be bottlenecking on your load balancer anyway), and there's resilience built in because you can use multiple NS records in your delegation (other servers will be used if one's down).


0

For Comodo issued certs Private Key: private_key.text Public Key Certificate: yourdomain.crt Certificate Chain: combine these 2 cat COMODORSADomainValidationSecureServerCA.crt COMODORSAAddTrustCA.crt > certchain.txt (or paste in COMODORSADomainValidationSecureServerCA.crt first followd by COMODORSAAddTrustCA.crt)


0

WWW2 or WWW3 may also refer to: Subdomain - part of a domain name identifying a website. World Wide Web - a system of interlinked, hypertext documents that runs over the Internet. typically used to identify a series of closely related websites within a domain, such as www.example.org, www2.example.org, and www3.example.org; the series may be continued ...


0

Did you maybe try to use something like: server HALB_ucd1 "${UCD1_END_POINT_IP}:${UCD1_END_POINT_PORT}" check port 8444


0

I've had to follow a similar approach for Umbraco in the past and have tended to allow authoring to run from one node only with a manual failover in the event that one host goes down. Depending on your needs you could split your front-end and authoring into three separate cloud services (using 4 hosts instead of 2) which would allow you to have SSL on ...


0

In the website world some people use ww2 to load balance and/or do A/B testing with "real user load" on a second cluster . Sometime its just a trick used to load with real user and do some benchmark on new stuff :)


6

It's used to load balance. You can use DNS to point www.example.com to one IP, www2.example.com to another IP, www3.example.com to yet another IP and so on and so on. And, in fact, this is how it's used. If you look at the DNS records for the domain, you should see an entry for www pointing to one IP, www2 pointing to another IP, and so on. It's a simple ...


0

You are using least_conn load balancing strategy in nginx for upstream PHP-FPM. This means that for one user that is at one IP address, might get served by a different PHP-FPM process. If these two PHP-FPM process don't share all necessary state between them about the user, then odd things can happen due to this. For example, if the user session state is ...


0

Since HAProxy only has layer 4 (TCP) and layer7 (HTTP) modes, it can't handle the GRE tunnels that PPTP controls. So in short, you can load-balance the control channel (with TCP mode), but not the actual tunnels.


0

You need to set the appropriate SELinux boolean to allow the web server to communicate with remote databases. setsebool -P httpd_can_network_connect_db 1


0

Your problem is the balance roundrobin line in HAProxy.cfg. This tells HAProxy to round-robin between all available nodes. Change it to something else (as detailed in the haproxy documentation) and you should get the behaviour you want. For posterity, the (IMO) most popular options to the 'balance' directive are: roundrobin - classic round-robin ...


2

You are not stating which protocol you are using, so I am assuming we are talking https. Each backend probably know some information about itself, which would uniquely identify that backend. That could be a hostname or a unicast IP address. The backend can include that information in appropriate locations. You could include it in a footer on each page. Or ...


8

If you want to be discreet, just have the webserver identify itself in a Server: response header (RFC 2616 Sec 14.38). For example, in Apache, the information returned in that header is controlled by the ServerTokens directive. Then, it's just a matter of inspecting the response headers in Firebug, Chrome DevTools, or Safari Web Inspector timeline. If you ...


0

Thanks @filmonic and Tero for correcting me, AS everyone suggested that redirection is not the best practice with POST request so I made changes in the architecture of my server side network. And it works. My Architecture now looks somewhat like this ________________ | | ...


1

You should fix your application so that it uses only https://domain.com/page or //domain.com/page format URLs. The redirection rule should be only used for a convenience for users so that they can make the first visit to the site by just typing the domain name.


3

You should not use redirect for post. If you have to, you should use 307 code for post. A end-user may be prompted about redirection. W3C Specifications - RFC 2616 301 Moved Permanently If the 301 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be ...



Top 50 recent answers are included