it seems to work (it now cross the php urls) but .... sometines it resolves http://192.168.0.2/news/?idnews=-58 instead of http://192.168.0.2/news/index.php3?idnews=-58 an idea ? > According to Greg: > > From: fx <[EMAIL PROTECTED]> > > > valid_extensions: .html .htm .shtml .php .php3 .asp .php > > > > > bad_extensions: .wav .gz .z .sit .au .zip .tar .hqx .exe .com .gif\ > > > .jpg .jpeg .aiff .class .map .ram .tgz .bin .rpm .mpg .mov .avi > > > > > > ... > > > pushing http://192.168.0.2/index.php3 > > > +A tag: pos = 2, position = =/news/index.php3?idnews=3 class=news> > > > href: http://192.168.0.2/news/index.php3?idnews=3 (La troisi?me) > > > > > > Rejected: Extension is not valid! > > > ... > > > > > > ... > > > *A tag: pos = 2, position = ="/services" class="navig1"> > > > href: http://192.168.0.2/services (services) > > > > > > Rejected: Extension is not valid! > > > ... > > > > i had the same troubles with .asp... > > solution: exclude php's from valid urls list. > > No, what fx wanted to do was to ensure that php's DID get indexed, so > excluding them is not an option. Fixing the valid_extensions handling > is the solution. I just need to know if the patch I posted yesterday > does that. ------------------------------------ To unsubscribe from the htdig mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this.
