On Sat, Apr 24, 2010 at 12:09 PM, Gary Webster <webster@xxxxxxxxxxx> wrote:
> Hello.
>
> I thought this might be simple, but I've not been able to find anything
> which works after much searching/experimenting.
>
> I have an application which submits a job to my webserver, then polls
> every few seconds for the output result file to be available.
> I am using NeoLoad (http://www.neotys.com/) to test my server.
> When the app (& NeoLoad) polls, & the file is not there (most of the
> time), Apache returns a 404 .
> There are many of these, so my NeoLoad results show many 'errors', & I can
> hardly tell if I have an actual error.
>
> So, I need either someone to tell me how to get NeoLoad to 'filter' 404s
> for a given filespec, or a lightweight way to have Apache rather return
> 204, or some such, for DocumentNotFound for a given filespec.
You could configure mod_rewrite to return 410 (Gone) for some of those
resources if that would help you differentiate.
You could also disable logging for the results file ("conditional logging")
--
Eric Covener
covener@xxxxxxxxx
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|