[Help] Image multiple request

[Gunz]

Hello guys, i need a little help about this feature.

My website are growing very fast, but now i want to protect my service. There are images that are posted on big sites and visited by thousand of people on the same times.

So now i want to tell you if it's possible for example resitrinct a requestion. For example every 60 seconds only 200 request on the SAME images, other requets go on "waiting" util the 60 seconds are passsed.

I was thinking it's possible to do with apache, but i don't know how. If anyone have some guides they are accepeted!

Cheers

 

[Rodolfo]

I have no idea on how do this, perhaps there is a module that do this job.

 

[Gunz]

I have no idea on how do this, perhaps there is a module that do this job.

I spoke with some people and all said me that apache can't hamdle all my requests and for static contenute is better lighttpd or ngix.

Are they supported now or continue to be not used?

ps: The apache modules that i installed are that, maybe can be usefull for someone.

mod_deflate
mod_bw
Zend Optimizer
eAccelerator
mod_cache
mod_Expires
mod_CBand

 

[Gunz]

Moved to nginx sucessfull Now i must find a solution about bandwidth....

 

[Rodolfo]

I spoke with some people and all said me that apache can't hamdle all my requests and for static contenute is better lighttpd or ngix.

Nginx is suitable for static and dynamic content but it doesn't have all the apache goodies. The best that you can do is apache+nginx and that setup I have on the demo. Few users are using nginx standalone , there is a guide for that in the server configuration and hosting forum.

 

[Gunz]

Nginx is AMAZING for static file. Finally i can run my server without Cloudflare. I'm handle 10.000.000+ requests every days.

Next step will be use apache for website and nginx for images.

 

[Rodolfo]

The best that you can do is to set-up nginx as a reverse proxy server with an Apache back end server. What does this means? it means that you will be able to handle the request with nginx and still get all the apache features like mod_rewrite, mod_deflate, .htaccess etc. http://www.cyberciti.biz/tips/using-nginx-as-reverse-proxy.html

This apache+nginx (or lighttpd) is the best way to improve the way that apache handle the requests. You will get all the nginx improvements but with no pain to make the applications work, no more try_files and things like that.