I think I may have figured out a different (and better) solution. After
going through the logs it appears that HTTrack was attempting to access
certain URLs using an irregular format, as well as the admin protected
pages. I will try excluding these from HTTrack and attempt testing it again.

In case anyone's curious, these are the ones I've identified so far:

-*:3000/domainStats<TR*
-*:3000/domainStats.</TABLE*
-*:3000/do</TABLE*
-*:3000/arro<*
-*:3000/purgeHost.html*
-*:3000/resetStats*
-*:3000/showU*
-*:3000/shut*
-*:3000/configNtop*
-*:3000/chang*
-*:3000/deleteU*
-*:3000/privacyFlag*
-*:3000/modifyU*

Thanks,
Mark

On Thu, Aug 23, 2012 at 2:42 AM, Mark Davis <[email protected]> wrote:

> All,
>
> I've been working on stripping out the NTOP webpages for reporting using
> HTTrack, and so far it seems to be working well with the exception of one
> problem. Every so often I'll get the "Rejected request" error message due
> to HTTrack having "previously sent ntop a bad request." Which is really
> slowing me down. I understand from researching this that URLSecurity can be
> disabled by commenting it out in http.c, but that would mean I would have
> to recompile it, right? (So far I've gotten away with just using sudo
> apt-get install ntop command so I wouldn't have to deal with that.) Is
> there a way to turn it off after it's been compiled, like from the Admin
> page?
>
> Thanks,
> Mark
>
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop

Reply via email to