Tag Info

Hot answers tagged

2

I wouldn't expect there to be much difference, if any, between Apache/Nginx/Lighttpd in this case. I would expect Apache to be slightly more memory heavy assuming you trimmed down all the modules that you don't need (which is likely most of them). My personal choice would be Lighttpd simply because I'm more familiar with it for serving static files and I've ...


2

This question reeks of premature optimization. I was hoping there would be something which would understand that one file is in high demand, for example when a new episode comes out, and would put it in a RAM cache. Can NGINX be used in that way? That's nothing you even need to worry about - it'll get cached by the OS and put into RAM the very first ...


2

First, we need a definition. Long-lived protocols are those for which the connection is intended to remain open indefinitely. (An example of such a protocol is ssh. While an ssh connection can be short, it is meant to be able to idle forever, thus the protocol is long-lived.) Short-lived protocols are more transactional in nature; a particular action ...


1

An HTTP request can be sent using one of the following methods: > Get() Issues the HTTP GET request. This method causes the web server to return the page requested. > Head() Issues the HTTP HEAD request. This method causes the web server to return just the headers of the response and none of the body. > Post() Issues the HTTP POST request. Use this ...


1

To get the HTTP requests to redirect instead of proxying, you should do two things: Move your proxying config (SSLProxyEngine through ProxyPassReverse into the SSL virtual host in /etc/httpd/conf.d/ssl.conf, so that it'll only apply there Create an HTTP virtual host which will redirect - probably in a new .conf file in /etc/httpd/conf.d: <VirtualHost ...


1

sshuttle works like an VPN but over SSH. Transparent proxy server that works as a poor man's VPN. Forwards over ssh. Doesn't require admin. Works with Linux and MacOS. Supports DNS tunneling. https://github.com/apenwarr/sshuttle


1

Praveen, if you are using at least PHP 5.4 this should help your PHP app: If you are using PGP 4.3 to 5.3, you can use header() instead (check the man pages for usage). Technically you can configure HAProxy to do what you ask, but it's probably more appropriate to simply modify your application to behave properly. At that point, HA Proxy should handle it ...


1

As per Monit's documentation: STATUS option can be used to explicitly test the HTTP status code returned by the HTTP server. If not used, the http protocol test will fail if the status code returned is greater than or equal to 400. You can override this behaviour by using the status qualifier. For example to test that a page does not exist (404 ...


1

You may be able to do so, by editing the ACL on the endpoint tab of your Web Role settings page. To do so: - Select the endpoint you would like to restrict access to and then click on Manage ACL [Defining ACL for the selected endpoint] [http://i.stack.imgur.com/Fsx4M.png] Then you may be able to deny access to others networks like done above Note: the ...


1

What you need is Proxy Pass, which are supported by both Apache and Nginx. Have a look at this page to give you an idea, http://wiki.nginx.org/LikeApache


1

Your redirection design seems to contradict each other, insofar ... 2 - Create and configure s3 bucket for www.mywebsite.com and redirect it to bucket created in step 1 using S3 bucket properties. ... redirect anyone accessing the Amazon S3 bucket for www.mywebsite.com to mywebsite.com, whereas ... 4 - Add forwarding to the top level domain ...


1

Use scientific method. Install monitoring. Gather statistics. Make decisions about your pinch points based on the information collected. Make changed based on the decisions made. Monitor the effectiveness of the change. Rinse and repeat.


1

I use nginx on my servers. Below is an example config that redirects traffic from port 80 to 8080: server { listen 80; server_name mysite.com; location / { proxy_pass http://127.0.0.1:8080/; } }


1

It DependsTM - some HTTP sessions are a few hundred millionseconds in length, others such as downloading a large resource or executing a slow REST call are a few seconds or minutes in length. Others can be much, much longer due to the use of keepalives. So no, I would not say that HTTP is exclusively short-lived.


1

First of all, fire and forget does not mean what you think it means. I highly recommend that you read more about this as it doesn't seem to be on-topic of the question. On-topic: Yes, keep-alive does permit sending multiple messages within the same TCP connection but usually you shall not assume that a session stays open as long as you want it or need it, ...



Only top voted, non community-wiki answers of a minimum length are eligible