@eyedeekay
&zzz
+R4SAS
+StormyCloud
+T3s|4
+acetone
+dr|z3d
+eche|off
+hk
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
BubbRubb
C341
Daddy
Danny
DeltaOreo
FreeRider
FreefallHeavens
HowardPlayzOfAdmin
Irc2PGuest43584
Irc2PGuest53893
Irc2PGuest82088
Irc2PGuest88009
Irc2PGuest88063
Onn4l7h
Onn4|7h
Over
RN
RN_
Sleepy
SlippyJoe
T3s|4_
aargh
ardu
b3t4f4c3___
cumlord
dr4wd3
duanin2
eyedeekay_bnc
hagen
llamafan717
mareki2p
nilbog-
nnm--
not_bob_afk
ohThuku1_
phil
poriori
profetikla
r00tobo
rapidash
shiver_
solidx66
thetia
uop23ip
w8rabbit
weko_
wew
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.