Item — HN Reader

If you don't like a user's request then don't service it and tell them why. You owe them nothing.

A simple 403 FORBIDDEN probably covers it. Or 429 TOO MANY REQUESTS might be appropriate. More bluntly, 204 NO CONTENT exists to tell your client, "I heard you just fine and I have nothing to say to you." Or there's 509 BANDWIDTH LIMIT EXCEEDED.

In any case, the protocols exist to give your client some constructive information in your refusal.

e: sp

1 comments

That only deals with types of requests, or the user making the request etc. It doesn't do anything about how the requested data/info etc is used. I suppose it is closer to a licence agreement. I don't think that there can be any technical way to enforce it only some sort of legal way.

Yes. Technology to restrict usage sounds a lot like DRM, which has many downsides. Enforcement, ultimately, will rely on good old fashioned copyright and licensing (contract) law.