@eyedeekay
&zzz
+R4SAS
+RN_
+Stormycloud
+T3s|4
+cumlord
+dr|z3d
+hagen
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
Arch
BubbRubb
Daddy_
Danny
DeltaOreo
FreefallHeavens
Guest99
Irc2PGuest13210
Irc2PGuest20240
Irc2PGuest21940
Irc2PGuest32330
Irc2PGuest74254
Irc2PGuest76033
Irc2PGuest78101
Onn4l7h
Onn4|7h
Over
Sisyphus
Sleepy
SlippyJoe
T3s|4_
Teeed
Uncrushed
aargh2
ac9f_
acetone_
b3t4f4c3___
dr4wd3
duanin2
erniee
eyedeekay_bnc
leopold
makoto
n1
nilbog-
not_blob
not_bob_afk
onon_
poriori_
profetikla
r00tobo
rapidash
shiver_
solidx66_
thetia
tr
u5657
uop23ip_
vivid_reader56
wodencafe2
x74a6
zelgomer
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.