@eyedeekay
&zzz
+RN
+RN_
+StormyCloud
+T3s|4
+altonen
+dr|z3d
+hk
+orignal
+postman
+qend-irc2p
+weko
+wodencafe
Arch
BubbRubb
Danny
DeltaOreo
FreefallHeavens
HowardPlayzOfAdmin1
Irc2PGuest44886
Irc2PGuest50191
Irc2PGuest59134
Irc2PGuest6854
Irc2PGuest90809
Leopold_
Onn4l7h
Onn4|7h
SigSegv
Sisyphus
Sleepy_
T3s|4_
acetone_
ardu
b3t4f4c3__
bak83
boonst
carried6590
cumlord
death
dr4wd3
eyedeekay_bnc
not_bob_afk
onon_
poriori
rapidash
shiver_
solidx66
thetia
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.