Re: WWW Form Bug Report: "Directory named .htaccess causes high CPU" on Irix

[Rob Hartill <ro...@imdb.com>]

Thanks for the info, I don't think we'd come across this problem
before.

cheers,
rob

dwatts@dimentech.com wrote:
>
>Submitter: dwatts@dimentech.com
>Operating system: Irix, version: 5.3
>Version of Apache Used: 1.1.1
>Extra Modules used: proxy_module,info_module,status_module,config_log_module,referer_log_module,action_module,imap_module,asis_module,env_module,alias_module,userdir_module,cgi_module,dir_module,includes_module, negotiation_module, auth_module, access_module, mime_module, core_module
>URL exhibiting problem: 
>
>Symptoms:
>--
>If a user creates a directory named .htaccess
>apache will start using up a lot of CPU. It appears
>that the server process goes into an infinite
>loop. More and more servers get created as the
>hung ones stop servicing requests. Asside from the
>high CPU usage, anyone trying to load a page from
>that directory would see the request hang as if
>the remote system was taking a very long time to
>satisfy the request.
>
>In our case, this was done by a user in their
>public_html/ directory. They had created .htaccess/
>and put a file called access in it. They now now
>how to create the .htaccess file correctly :-)
>--
>
>Backtrace:
>--
>
>--
>


-- 
Rob Hartill (robh@imdb.com)    
http://www.imdb.com/  ... why wait for a clear night to see the stars?.

Re: WWW Form Bug Report: "Directory named .htaccess causes high CPU" on Irix

[Paul Sutton <pa...@ukweb.com>]

On Sat, 12 Oct 1996, Rob Hartill wrote:
> Thanks for the info, I don't think we'd come across this problem
> before.

Something very similar was also reported on 3 Sept on a Linux system, but
I cannot reproduce it on either Linux or IRIX.

Paul

> dwatts@dimentech.com wrote:
> >If a user creates a directory named .htaccess
> >apache will start using up a lot of CPU. It appears
> >that the server process goes into an infinite
> >loop. More and more servers get created as the
> >hung ones stop servicing requests. Asside from the
> >high CPU usage, anyone trying to load a page from
> >that directory would see the request hang as if
> >the remote system was taking a very long time to
> >satisfy the request.