@eyedeekay
&eche|on
&zzz
+R4SAS
+RN
+RN_
+StormyCloud
+T3s|4
+acetone
+cumlord
+dr|z3d
+eche|off
+mareki2p
+orignal
+postman
+snex
+wodencafe
Arch
BubbRubb
Chrono
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest16752
Irc2PGuest51880
Irc2PGuest61924
Irc2PGuest67617
Onn4l7h
Sisyphus
Sleepy_
T3s|4_
Teeed
aargh2
ac9f
b3t4f4c3__
bak83_
duanin2
duck
guest333
john231
leopold
makoto
nilbog
not_bob_afk
ntty
poriori
profetik1
r00tobo_BNC
rapidash
shiver_
solidx66
thetia
tr
u0_a194
u5657
uop23ip
vivid_reader56
w8rabbit
x74a6
xHarr
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.