one-to-many messaging

[PeteM]

Matthew Pemble wrote  on 2-04-08 09:15:
> 
> However the RFC text makes it clear that a 404 is a technically 
> legitimate (I'll leave the lawyering to somebody else) response:
> 
> 
>         10.4.4 403 Forbidden
> 
>    The server understood the request, but is refusing to fulfill it.
>    Authorization will not help and the request SHOULD NOT be repeated.
> 
>    If the request method was not HEAD and the server wishes to make
>    public why the request has not been fulfilled, it SHOULD describe the
>    reason for the refusal in the entity.  If the server does not wish to
>    make this information available to the client, the status code 404
>    (Not Found) can be used instead.


But it's not the server that is supplying the fake 404. It's a third 
party machine between the server and the requesting client.

-- 
Pete Mitchell