@eyedeekay
&kytv
&zzz
+R4SAS
+RN
+StormyCloud
+T3s|4
+acetone
+dr|z3d
+hagen
+hk
+lbt
+orignal
+postman
+weko
+wodencafe
Arch
Danny
DeltaOreo
FreefallHeavens_
Irc2PGuest12249
Irc2PGuest25220
Irc2PGuest54664
Irc2PGuest59134
Irc2PGuest90091
Irc2PGuest90883
Irc2PGuest92478
Leopold_
Nausicaa
Onn4l7h
Onn4|7h
Sleepy
Soni
T3s|4_
Teeed
aeiou
aisle1
ardu
b3t4f4c3___
bak83_
boonst
dickless
dr4wd3_
enoxa
eyedeekay_bnc
foobar_
mareki2p
not_bob_afk
poriori_
profetikla
qend-irc2p
radakayot_
rapidash
shiver_
solidx66
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.