(please note the quotes around securing).

I really love the SlingPostServlet and the fact that I can create JCR
structure starting from a JSON stream. It really ease the process for
creating (and updating?) content.

Now if I'd go for the usage of it, I'd like to prevent some malicious
teenager to use curl commands to POST fake/not-correct content to the
repository.

I know that I can restrict it with user/password but what if he has the
right credentials?

Are there any way to restrict the operations allowed by the PostServlet?

Enforcing some content structures?

Prevent "flooding"?

Cheers
Davide

Reply via email to