@eyedeekay
&zzz
+R4SAS
+RN
+T3s|4
+acetone
+altonen
+dr|z3d
+hagen
+hk
+orignal
+postman
+qend-irc2p
+snex
+weko
+wodencafe
+y2kboy23
Arch
BubbRubb1
Daddy
Daddy_1
Danny
DeltaOreo
FreeB
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest31631
Irc2PGuest41581
Irc2PGuest92548
Irc2PGuest95056
Leopold
Onn4l7h
Onn4|7h
Sisyphus
Sleepy
SlippyJoe_
StormyCloud_
T3s|4_
T3s|4__
Teeed
ardu
b3t4f4c3___
bak83_
boonst
defaultnick
dr4wd3_
eyedeekay_bnc
guest7621
not_bob_afk
not_human_
poriori_
profetikla
r00tobo
rapidash
shiver_
solidx66_
thetia
tr
u5657
uop23ip
w8rabbit
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.