4

how do reverse proxies know which content is static?

view full story
linux-howto

http://serverfault.com – I was looking at the setup of reverse proxies, like nginx in front of apache, to reduce load on webservers for serving static content. For any given URL, our web pages will have different parts static and dynamic. How do reverse proxies know when to serve resources themselves, or pull it from the source web server behind them? Obviously things like images and javascript files are static, but even some of those, like captchas, are dynamically generated. Our drupal sites actually look at the path in the url and serve different content accordingly, taking path elements as arguments. Does it si (HowTos)

dayu's picture
Submitted by dayu on 02/02/2012 – Made popular on 02/02/2012

Stories similar to how do reverse proxies know which content is static?

My question is there any advantage using nginx as reverse proxy when most of the content is dynamically generated via php ?

As far as i am concern the nginx is very useful in caching the static content into a cache and serving the multiple requests at once ..

is this true ? or is there any other advantages of the running nginx as a reverse proxy in mostly php driven dynamic content websites ?

Nginx is a web server / proxy server, according to Wikipedia, this is the description:

We are using nginx to serve static content and apache for dynamic content.

I have defined a default server configuration as:

#Set a default server that simply proxies all requests to apache server { listen 80 default_server; server_name _;

location / { proxy_pass http://127.0.0.1:8080; } }

Is the the best way to proxy everything to apache if for some reason a ser

I'm using Apache to serve static content, and then reverse proxy-ing to a Rails server to process dynamic content, some of which can take a long time to generate.

I have an nginx server sitting in front of apache running django.

Most of my site is static content: http://www.grovemade.com/

My app server can handle the pieces that needs to be dynamic just fine (POST, cart, order status, faq, etc.).

A far far majority of hits are to static pages like product pages, about pages, ajax get requests.

It handles like a champ serving pages straight out of memcac

I have a dynamic webpage which I want to create a "frozen" copy of.

Typically I would do something like wget -m http://example.com, and then put the files in the document root of the web-server.

This site however has some dynamic content, including dynamically generated images, for instance

http://example.com/company/123/logo

This means that in order to mirror the page, I need to

Save whate

I've an Nginx as a reverse Proxy for static content. And an Apache for dynamic content.

I'm considering using 2 virtual servers, 1 running Apache facing the internet (e.g. www.example.com) running over https and other running ngnix on a private ip connecting to the main server to serve static content e.g. /data (css, PDF's, etc). The machines will both be hosted in a VM environment both running on the same network.

I use a webserver as a mobile app backend, which doesn't serve any static content. In fact even images are loaded from the database (MongoDB) and served dynamically.

I'm asking myself if in that case are there any advantages when moving from Apache to Nginx. Instead of one apache process there is one PHP-FPM process needed for each concurrent connection.