Hi
Are you running PHP with CGI? If yes, then you can use the
Directory/Directory directive blocks and the Options Directive to
optionally allow or disallow execution of PHP scripts. For example, your
basic hosting can have a config:
Directory /var/www/basic
Options -ExecCGI other options
The apache I'm running is reverse proxy with SSL and these are my settings
IfModule expires_module
ExpiresActive On
ExpiresDefault A0
ExpiresByType image/gif access plus 3600 seconds
ExpiresByType image/png access plus 3600 seconds
ExpiresByType image/jpg
2009/7/2 Chandranshu . chandran...@gmail.com:
Hi
Are you running PHP with CGI? If yes, then you can use the
Directory/Directory directive blocks and the Options Directive to
optionally allow or disallow execution of PHP scripts. For example, your
basic hosting can have a config:
Directory
El jue, 02-07-2009 a las 00:26 +0200, André Warnier escribió:
So far, I think the score is more like mod_cache 10 / Developer 0
What is this?
Thanks a lot.
Thanks for your help.
if (r-method_number != M_GET)
{
return DECLINED;
}
--
--
--
Publicidad y Servicios
Hi,
Someone suggests an idea of how I would prioritize requests ina webserver.
Requests with more priorities are processed first than less priorities.
I don't have any idea.
Thank You
Ricardo
--
View this message in context:
Can you provide a practical example of what you're trying to achieve?
This sounds like a violation of net-neutrality, but anyway most web
requests shouldn't take longer than a second or two anyway so I don't
know what kind of performance boost your top-tier customers can
reasonably expect with
Hi,
Imagine a queue with many requests for low priority (requests_low), after
arrive a request high priority (request_high).
Request_high is then processed first than others. Provide QoS (Quality of
Service)
Thank you
Ricardo
On Thu, Jul 2, 2009 at 4:56 PM, Jonathan Zuckerman
On Thu, Jul 2, 2009 at 1:06 PM, ricardo
figueiredoricardoogra...@gmail.com wrote:
Hi,
Imagine a queue with many requests for low priority (requests_low), after
arrive a request high priority (request_high).
Request_high is then processed first than others. Provide QoS (Quality of
Service)
Hi,
That's the question. I dont have any idea.
I think rename the process (Ex: httpd_high and httpd_low), or add some
variable.
I dont know !!! Do you have any idea ???
Ricardo
On Thu, Jul 2, 2009 at 5:09 PM, Jonathan Zuckerman j.zucker...@gmail.comwrote:
On Thu, Jul 2, 2009 at 1:06 PM,
RewriteEngine On
RewriteCond %{REQUEST_URI} ^http\:\/\/.*\.com$
RewriteRule - [F]
On Wed, Jul 1, 2009 at 6:26 AM, bf...@free-man.net bf...@free-man.netwrote:
I have a major attach of URL being sent:
http://mydomain.com/http://someurl.com
so the http:/someurl.com is requested from my apache
Or you can use mod_security instead it will protect you from XSS and SQL
injection attacks and some other nasty stuff :)
On Fri, Jul 3, 2009 at 10:23 AM, Igor Cicimov icici...@gmail.com wrote:
RewriteEngine On
RewriteCond %{REQUEST_URI} ^http\:\/\/.*\.com$
RewriteRule - [F]
On Wed, Jul 1,
It was thus said that the Great ricardo figueiredo once stated:
That's the question. I dont have any idea.
If you have no idea how to prioritize the requests, then I doubt you'll
get much help. Prioritization of requests can happen in the router, a
load balancer or the actual webserver.
12 matches
Mail list logo