Re: [us...@httpd] Apache's strange

I'm not. But If components (CPU, disk IO, ...) are overloaded the value of response time increases and not stabilize. For example: req/s = 500 > 1.23 seconds req/s = 1000 > 2.44 seconds req/s = 1500 > 5.78 seconds req/s = 2000 > 10.5 seconds req/s = 3000 > 17.5 seconds req/s

Re: [us...@httpd] Apache's strange

On Sat, Oct 24, 2009 at 1:10 PM, ricardo13 wrote: > > hi, > > I'm doing some tests with reverse proxy in Apache Web Server. > I use HTTPERF to stress the server. > > I imagine that load (requests/seg) increase consequently the response time > also increase. > But this doesn't happen. > > At one po

Re: [us...@httpd] GET request on a directory

On Saturday, October 24, 2009, Doug McNutt wrote: >>On Fri, Oct 23, 2009 at 12:30 PM, I wrote: >>> GET requests which would otherwise look for an index.html file but are set >>> up with something like this: >>> >>> HTTP://domain.com/somedirectory/?C=xx;O=yy >>> >>> seem to reply with a formatted

[us...@httpd] Apache's strange

hi, I'm doing some tests with reverse proxy in Apache Web Server. I use HTTPERF to stress the server. I imagine that load (requests/seg) increase consequently the response time also increase. But this doesn't happen. At one point, the values of response time stabilize and dont increase. My dou

Re: [us...@httpd] GET request on a directory

>On Fri, Oct 23, 2009 at 12:30 PM, I wrote: >> GET requests which would otherwise look for an index.html file but are set >> up with something like this: >> >> HTTP://domain.com/somedirectory/?C=xx;O=yy >> >> seem to reply with a formatted list of directory contents. Can someone >> point me to s

RE: [us...@httpd] Help: HTTP response has wrong Content-Type field

Thank you very much for the response. We finally got the root cause. When we used the following code to set content type, there will be problem. The reason is that Apache ap_set_content_type does not copy the content to request_rec::content_type, it only use the "const char*" pointer. When our_

Re: [us...@httpd] Handler Chain (based on request method)

Aaron Dalton wrote: I'm using mod_perl and CGI::Application::Dispatch to create a RESTful web application. In the one resource, GETs should be sent to the default handler, and all other requests to the dispatcher. I have tried using and , but they do not appear to be working. The handlers g

Re: [us...@httpd] Restrict Proxy by method

On 24 Oct 2009, at 13:18, Aaron Dalton wrote: Is there a way to tell a proxy server to only forward requests using a particular method (GET, POST, etc...)? I have a web app with a front and back end server. I want the front end to pass along all GETs to the back, but reject all other met

[us...@httpd] Restrict Proxy by method

Is there a way to tell a proxy server to only forward requests using a particular method (GET, POST, etc...)? I have a web app with a front and back end server. I want the front end to pass along all GETs to the back, but reject all other methods. I've been using , but that does not work. I

[us...@httpd] Handler Chain (based on request method)

I'm using mod_perl and CGI::Application::Dispatch to create a RESTful web application. In the one resource, GETs should be sent to the default handler, and all other requests to the dispatcher. I have tried using and , but they do not appear to be working. The handlers get processed regardle