On Nov 23, 2005, at 12:51 PM, mario ruggier wrote:

> Hi,
>
> just stumbled on this by accident....
>
> If I run a qp site, say for example, we use the proto example of
> qp, with its default settings, i.e. durus server on 7002, qp web
> server on 8002 (actually I added a "max_children: 1" entry to its
> configuration dict) :
>
> $ qp -s proto start
> durus[4240] started at 2005-11-23 17:36:06.989118 UTC
> durus[Ready with 9 objects]
> web[4241] started at 2005-11-23 17:36:07.049744 UTC
> $ ps -aux | grep pyth
> mario   4240   0.0  0.4    36360   1872 std  S     6:36PM   0:00.04
> python /Library/Frameworks/Python.framework/Versions/2.4/bin/qp -s
> proto start
> mario   4241   0.0  0.3    36360   1344 std  S     6:36PM   0:00.04
> python /Library/Frameworks/Python.framework/Versions/2.4/bin/qp -s
> proto start
> mario   4242   0.0  0.4    36360   1968 std  S     6:36PM   0:00.03
> python /Library/Frameworks/Python.framework/Versions/2.4/bin/qp -s
> proto start
> mario   4244   0.0  0.0    18644     92 std  R+    6:36PM   0:00.00
> grep pyth
> $
>
> Then I view with a browser the URL: http://localhost:8002/database/
> it is just fine...
>
> If, however, I load this URL instead: http://localhost:7002/database/
> the browser comes back with the message that "can’t open the page
> “http://localhost:7002/database/” because it could not load any
> data from this location", which is just fine. But, at this point:

The durus client/server protocol is intended only for connection from
a compliant durus client_storage:  all other connections are, for
practical purposes, hostile.    This is good to know about, but I
don't think
there is anything here to fix.  If someone is sending non-compliant
messages
to the durus server, then shutting it down is reasonable.