Re: Discussion about Cancel-Lock support
Julien ÉLIE <[email protected]>
| Newsgroups | gmane.network.inn |
|---|---|
| Message-ID | <[email protected]> |
Hi Sergey, >> Now that Cancel-Lock has been standardized in RFC 8315, maybe it is a >> good time to integrate its support in INN. At last! >> >> We already have an old ticket about that, with patches against INN 2.3.5 >> (that need being rewritten): >> https://inn.eyrie.org/trac/ticket/33 > > I seen in ChangeLog of inn-2.6.2: > > 2018-03-10 iulius > ... > * Add check for unique Cancel-Key and Cancel-Lock header fields > (RFC 8315) in nnrpd > > Is it not support of RFC 8315? Or is it just the initial stage? No, it is not support of RFC 8315, but only the addition of an easy check that these header fields are present only once, if any, when a user posts an article. Currently, if you want INN to support RFC 8315, you need using filter hooks, like this one for nnrpd (page in German): https://netz-rettung-recht.de/archives/1473-INN-Cancel-Lock-und-Cancel-Key.html INN does not natively implement RFC 8315, but can have the feature through filter hooks. I hope to implement it natively for INN 2.7.0 (or 2.6.5). -- Julien ÉLIE « J'aime les calculs faux car ils donnent des résultats plus justes. » (Jean Arp) _______________________________________________ inn-workers mailing list [email protected] https://lists.isc.org/mailman/listinfo/inn-workers