@eyedeekay
&Irc2PGuest88200
&zzz
+R4SAS
+RN
+dr|z3d
+eche|off
+hagen
+not_bob_afk
+postman
+snex
+wodencafe
Arch2
Danny
DeltaOreo
FreeB
FreefallHeavens
Irc2PGuest59134
Irc2PGuest59581
Irc2PGuest70083
Irc2PGuest96449
Irc2PGuest97049
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
T3s|4_
T3s|4__
acetone_
aeiou
ardu
b3t4f4c3___
bak83_
boonst
carried6590
cumlord
death
dr4wd3
duck
eyedeekay_bnc
mareki2p_
onon_
orignal_
phobos
pisslord
poriori_
profetikla
qend-irc2p
radakayot_
rapidash
shiver_1
solidx66
thetia
u5657
uop23ip
w8rabbit
weko_
x74a6
RN
Is there a way to blackhole things in the default Jetty server?
RN
I'm seeing Wordpress subdirectory requests on my eepsite, and I do not run Wordpress.
RN
I would like to send no response to such crawling.
RN
Currently, my eepsite will send a 404 response. but I'd like to make certain requested URLs not send anything....
RN
candidates currently include *Seedless/*, and *Wordpress/* as requests I'd like to send no response for but jetty defaults to sending a 404
RN
I DO want to allow easy acces to directories under docroot that do exist
RN
but I do not want to respond to random probes
RN
the jetty docs did not make obvious any easy mechanism, or my search-foo was flawed
dr|z3d
RN: blocking clients accessing definable urls on the server is something tunnel filtering would be good for, if implemented.