@eyedeekay
&eche|on
&zzz
+R4SAS
+RN_
+StormyCloud
+acetone
+cumlord
+dr|z3d
+eche|off
+mareki2p
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
BubbRubb
Chrono
Danny
DeltaOreo
Irc2PGuest35958
Irc2PGuest49308
Irc2PGuest51170
Irc2PGuest51586
Irc2PGuest64807
Irc2PGuest85653
Irc2PGuest96178
Onn4l7h
Over1
RN
Sisyphus
Sleepy
SlippyJoe_
T3s|4_
Teeed
aargh2
ac9f
b3t4f4c3___
dr4wd3
duanin2
eyedeekay_bnc
leopold_
nilbog
nnm--
not_bob_afk
null911
onon_
poriori
profetikla
r00tobo_BNC
shiver_
solidx66
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.