Send inn-workers mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."
Today's Topics:
1. Re: Discussion about Cancel-Lock support (Sergey)
2. Re: Discussion about Cancel-Lock support (Julien ?LIE)
----------------------------------------------------------------------
Message: 1
Date: Fri, 8 Jan 2021 16:07:27 +0400
From: Sergey <[email protected]>
To: [email protected]
Subject: Re: Discussion about Cancel-Lock support
Message-ID: <[email protected]>
Content-Type: Text/Plain; charset="utf-8"
On Sunday 08 November 2020, Julien wrote:
> 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?
--
Regards,
Sergey
------------------------------
Message: 2
Date: Fri, 8 Jan 2021 14:00:39 +0100
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: Discussion about Cancel-Lock support
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
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)
------------------------------
Subject: Digest Footer
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
------------------------------
End of inn-workers Digest, Vol 127, Issue 7
*******************************************
